Apparatus and method for sending and receiving broadcast signals

ABSTRACT

Disclosed is an apparatus for transmitting a broadcast signal including: an input formatter module configured to de-multiplex an input stream into at least one data pipe (DP); a BICM module configured to perform error correction on data of the at least one DP; a frame building module configured to generate a signal frame including the data of the DP; and an OFDM generation module configured to generate a transmission signal by inserting a preamble into the signal frame and performing OFDM modulation thereon.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to Provisional Application No.61/939,280 filed on 13 Feb., 2014 in US, the entire contents of which ishereby incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention relates to an apparatus for transmitting broadcastsignals, an apparatus for receiving broadcast signals and methods fortransmitting and receiving broadcast signals.

Discussion of the Related Art

As analog broadcast signal transmission comes to an end, varioustechnologies for transmitting/receiving digital broadcast signals arebeing developed. A digital broadcast signal may include a larger amountof video/audio data than an analog broadcast signal and further includevarious types of additional data in addition to the video/audio data.

That is, a digital broadcast system can provide HD (high definition)images, multi-channel audio and various additional services. However,data transmission efficiency for transmission of large amounts of data,robustness of transmission/reception networks and network flexibility inconsideration of mobile reception equipment need to be improved fordigital broadcast.

SUMMARY OF THE INVENTION

An object of the present invention is to provide an apparatus and methodfor transmitting broadcast signals to multiplex data of a broadcasttransmission/reception system providing two or more different broadcastservices in a time domain and transmit the multiplexed data through thesame RF signal bandwidth and an apparatus and method for receivingbroadcast signals corresponding thereto.

Another object of the present invention is to provide an apparatus fortransmitting broadcast signals, an apparatus for receiving broadcastsignals and methods for transmitting and receiving broadcast signals toclassify data corresponding to services by components, transmit datacorresponding to each component as a data pipe, receive and process thedata

Still another object of the present invention is to provide an apparatusfor transmitting broadcast signals, an apparatus for receiving broadcastsignals and methods for transmitting and receiving broadcast signals tosignal signaling information necessary to provide broadcast signals.

Accordingly, it is an object of the present invention is to provide anapparatus for transmitting a broadcast signal, the apparatus comprising:an input formatter module configured to de-multiplex an input streaminto at least one data pipe (DP); a BICM module configured to performerror correction on data of the at least one DP; a frame building moduleconfigured to generate a signal frame including the data of the DP; andan OFDM generation module configured to generate a transmission signalby inserting a preamble into the signal frame and performing OFDMmodulation, wherein the input formatting module comprises: a headercompression module configured to compress IP headers of IP packetsincluded in an IP stream when the input stream is the IP stream; abaseband (BB) frame slicer module configured to allocate data of the IPpackets to a BB frame; and a BB frame header insertion module configuredto insert a BB frame header into the BB frame.

Another object of the present invention is to provide an apparatus forreceiving a broadcast signal, the apparatus comprising: asynchronization/demodulation module configured to perform signaldetection and OFDM demodulation on a received broadcast signal; a frameparsing module configured to parse a signal frame of the broadcastsignal to extract service data; a demapping/decoding module configuredto convert an input signal into a bit domain and perform deinterleavingon the converted bit domain; and an output processing module configuredto receive the service data and output a data stream, wherein the outputprocessing module comprises: a baseband (BB) frame header parser moduleconfigured to parse a BB frame header to obtain IP header compressioninformation; a header de-compression module configured to de-compressheaders of IP packets included in the BB frame by using the IP headercompression information; and a packet recombining module configured tocombine the IP packets to output an IP stream.

The present invention can process data according to servicecharacteristics to control QoS (Quality of Services) for each service orservice component, thereby providing various broadcast services.

The present invention can achieve transmission flexibility bytransmitting various broadcast services through the same RF signalbandwidth.

The present invention can improve data transmission efficiency andincrease robustness of transmission/reception of broadcast signals usinga MIMO system.

According to the present invention, it is possible to provide broadcastsignal transmission and reception methods and apparatus capable ofreceiving digital broadcast signals without error even with mobilereception equipment or in an indoor environment.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a structure of an apparatus for transmittingbroadcast signals for future broadcast services according to anembodiment of the present invention.

FIG. 2 illustrates an input formatting block according to one embodimentof the present invention.

FIG. 3 illustrates an input formatting block according to anotherembodiment of the present invention.

FIG. 4 illustrates an input formatting block according to anotherembodiment of the present invention.

FIG. 5 illustrates a BICM block according to an embodiment of thepresent invention.

FIG. 6 illustrates a BICM block according to another embodiment of thepresent invention.

FIG. 7 illustrates a frame building block according to one embodiment ofthe present invention.

FIG. 8 illustrates an OFDM generation block according to an embodimentof the present invention.

FIG. 9 illustrates a structure of an apparatus for receiving broadcastsignals for future broadcast services according to an embodiment of thepresent invention.

FIG. 10 illustrates a frame structure according to an embodiment of thepresent invention.

FIG. 11 illustrates a signaling hierarchy structure of the frameaccording to an embodiment of the present invention.

FIG. 12 illustrates preamble signaling data according to an embodimentof the present invention.

FIG. 13 illustrates PLS1 data according to an embodiment of the presentinvention.

FIG. 14 illustrates PLS2 data according to an embodiment of the presentinvention.

FIG. 15 illustrates PLS2 data according to another embodiment of thepresent invention.

FIG. 16 illustrates a logical structure of a frame according to anembodiment of the present invention.

FIG. 17 illustrates PLS mapping according to an embodiment of thepresent invention.

FIG. 18 illustrates EAC mapping according to an embodiment of thepresent invention.

FIG. 19 illustrates FIC mapping according to an embodiment of thepresent invention.

FIG. 20 illustrates a type of DP according to an embodiment of thepresent invention.

FIG. 21 illustrates DP mapping according to an embodiment of the presentinvention.

FIG. 22 illustrates an FEC structure according to an embodiment of thepresent invention.

FIG. 23 illustrates a bit interleaving according to an embodiment of thepresent invention.

FIG. 24 illustrates a cell-word demultiplexing according to anembodiment of the present invention.

FIG. 25 illustrates a time interleaving according to an embodiment ofthe present invention.

FIG. 26 is a view illustrating a mode adaptation module of a broadcastsignal transmitter according to an embodiment of the present invention.

FIG. 27 is a view illustrating an output processor module of a broadcastsignal receiver according to an embodiment of the present invention.

FIG. 28 is a view illustrating a method of compressing an IP headeraccording to an embodiment of the present invention.

FIG. 29 is a view illustrating a method of compressing an IP headeraccording to another embodiment of the present invention.

FIG. 30 is a view illustrating a method of signaling header compressioninformation according to an embodiment of the present invention.

FIG. 31 is a view illustrating a method of signaling header compressioninformation according to another embodiment of the present invention.

FIG. 32 is a view illustrating a method of signaling header compressioninformation according to another embodiment of the present invention.

FIG. 33 is a view illustrating an embodiment of a scheme of expressing apacket length of FIG. 32.

FIG. 34 is a view illustrating a BB frame configuration of IP headercompression methods according to an embodiment of the present invention.

FIG. 35 is a view illustrating a BB frame configuration of IP headercompression methods and an error checking method according to anembodiment of the present invention.

FIG. 36 is a view illustrating a BB frame configuration of IP headercompression methods and a packet accessing method according to anembodiment of the present invention.

FIG. 37 is a view illustrating a BB frame configuration and a packetaccessing method according to an embodiment of the present invention.

FIG. 38 is a view illustrating a method for transmitting a broadcastsignal according to an embodiment of the present invention.

FIG. 39 is a view illustrating a method for receiving a broadcast signalaccording to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that can be implemented according to the present invention.The following detailed description includes specific details in order toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details.

Although most terms used in the present invention have been selectedfrom general ones widely used in the art, some terms have beenarbitrarily selected by the applicant and their meanings are explainedin detail in the following description as needed. Thus, the presentinvention should be understood based upon the intended meanings of theterms rather than their simple names or meanings. Also, the term blockand module are used similarly to indicate logical/functional unit ofparticular signal/data processing.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, aUHDTV service, etc. The present invention may process broadcast signalsfor the future broadcast services through non-MIMO (Multiple InputMultiple Output) or MIMO according to one embodiment. A non-MIMO schemeaccording to an embodiment of the present invention may include a MISO(Multiple Input Single Output) scheme, a SISO (Single Input SingleOutput) scheme, etc.

While MISO or MIMO uses two antennas in the following for convenience ofdescription, the present invention is applicable to systems using two ormore antennas.

The present invention may defines three physical layer (PL)profiles—base, handheld and advanced profiles-each optimized to minimizereceiver complexity while attaining the performance required for aparticular use case. The physical layer (PHY) profiles are subsets ofall configurations that a corresponding receiver should implement.

The three PHY profiles share most of the functional blocks but differslightly in specific blocks and/or parameters. Additional PHY profilescan be defined in the future. For the system evolution, future profilescan also be multiplexed with the existing profiles in a single RFchannel through a future extension frame (FEF). The details of each PHYprofile are described below.

1. Base Profile

The base profile represents a main use case for fixed receiving devicesthat are usually connected to a roof-top antenna. The base profile alsoincludes portable devices that could be transported to a place butbelong to a relatively stationary reception category. Use of the baseprofile could be extended to handheld devices or even vehicular by someimproved implementations, but those use cases are not expected for thebase profile receiver operation.

Target SNR range of reception is from approximately to 20 dB, whichincludes the 15 dB SNR reception capability of the existing broadcastsystem (e.g. ATSC A/53). The receiver complexity and power consumptionis not as critical as in the battery-operated handheld devices, whichwill use the handheld profile. Key system parameters for the baseprofile are listed in below table 1.

TABLE 1 LDPC codeword length 16K, 64K bits Constellation size 4~10 bpcu(bits per channel use) Time de-interleaving memory size ≦2¹⁹ data cellsPilot patterns Pilot pattern for fixed reception FFT size 16K, 32Kpoints

2. Handheld Profile

The handheld profile is designed for use in handheld and vehiculardevices that operate with battery power. The devices can be moving withpedestrian or vehicle speed. The power consumption as well as thereceiver complexity is very important for the implementation of thedevices of the handheld profile. The target SNR range of the handheldprofile is approximately 0 to 10 dB, but can be configured to reachbelow 0 dB when intended for deeper indoor reception.

In addition to low SNR capability, resilience to the Doppler Effectcaused by receiver mobility is the most important performance attributeof the handheld profile. Key system parameters for the handheld profileare listed in the below table 2.

TABLE 2 LDPC codeword length 16 Kbits Constellation size 2~8 bpcu Timede-interleaving memory size ≦2¹⁸ data cells Pilot patterns Pilotpatterns for mobile and indoor reception FFT size 8K, 16K points

3. Advanced Profile

The advanced profile provides highest channel capacity at the cost ofmore implementation complexity. This profile requires using MIMOtransmission and reception, and UHDTV service is a target use case forwhich this profile is specifically designed. The increased capacity canalso be used to allow an increased number of services in a givenbandwidth, e.g., multiple SDTV or HDTV services.

The target SNR range of the advanced profile is approximately 20 to 30dB. MIMO transmission may initially use existing elliptically-polarizedtransmission equipment, with extension to full-power cross-polarizedtransmission in the future. Key system parameters for the advancedprofile are listed in below table 3.

TABLE 3 LDPC codeword length 16K, 64 Kbits Constellation size 8~12 bpcuTime de-interleaving memory size ≦2¹⁹ data cells Pilot patterns Pilotpattern for fixed reception FFT size 16K, 32K points

In this case, the base profile can be used as a profile for both theterrestrial broadcast service and the mobile broadcast service. That is,the base profile can be used to define a concept of a profile whichincludes the mobile profile. Also, the advanced profile can be dividedadvanced profile for a base profile with MIMO and advanced profile for ahandheld profile with MIMO. Moreover, the three profiles can be changedaccording to intention of the designer.

The following terms and definitions may apply to the present invention.The following terms and definitions can be changed according to design.

auxiliary stream: sequence of cells carrying data of as yet undefinedmodulation and coding, which may be used for future extensions or asrequired by broadcasters or network operators

base data pipe: data pipe that carries service signaling data

baseband frame (or BBFRAME): set of Kbch bits which form the input toone FEC encoding process (BCH and LDPC encoding)

cell: modulation value that is carried by one carrier of the OFDMtransmission

coded block: LDPC-encoded block of PLS1 data or one of the LDPC-encodedblocks of PLS2 data

data pipe: logical channel in the physical layer that carries servicedata or related metadata, which may carry one or multiple service(s) orservice component(s).

data pipe unit: a basic unit for allocating data cells to a DP in aframe.

data symbol: OFDM symbol in a frame which is not a preamble symbol (theframe signaling symbol and frame edge symbol is included in the datasymbol)

DP_ID: this 8-bit field identifies uniquely a DP within the systemidentified by the SYSTEM_ID

dummy cell: cell carrying a pseudo-random value used to fill theremaining capacity not used for PLS signaling, DPs or auxiliary streams

emergency alert channel: part of a frame that carries EAS informationdata

frame: physical layer time slot that starts with a preamble and endswith a frame edge symbol

frame repetition unit: a set of frames belonging to same or differentphysical layer profile including a FEF, which is repeated eight times ina super-frame

fast information channel: a logical channel in a frame that carries themapping information between a service and the corresponding base DP

FECBLOCK: set of LDPC-encoded bits of a DP data

FFT size: nominal FFT size used for a particular mode, equal to theactive symbol period Ts expressed in cycles of the elementary period T

frame signaling symbol: OFDM symbol with higher pilot density used atthe start of a frame in certain combinations of FFT size, guard intervaland scattered pilot (sp) pattern, which carries a part of the PLS data

frame edge symbol: OFDM symbol with higher pilot density used at the endof a frame in certain combinations of FFT size, guard interval andscattered pilot pattern

frame-group: the set of all the frames having the same PHY profile typein a super-frame.

future extension frame: physical layer time slot within the super-framethat could be used for future extension, which starts with a preamble

Futurecast UTB system: proposed physical layer broadcasting system, ofwhich the input is one or more MPEG2-TS or IP or general stream(s) andof which the output is an RF signal

input stream: A stream of data for an ensemble of services delivered tothe end users by the system.

normal data symbol: data symbol excluding the frame signaling symbol andthe frame edge symbol

PHY profile: subset of all configurations that a corresponding receivershould implement

PLS: physical layer signaling data consisting of PLS1 and PLS2

PLS1: a first set of PLS data carried in the FSS symbols having a fixedsize, coding and modulation, which carries basic information about thesystem as well as the parameters needed to decode the PLS2

NOTE: PLS1 data remains constant for the duration of a frame-group.

PLS2: a second set of PLS data transmitted in the FSS symbol, whichcarries more detailed PLS data about the system and the DPs

PLS2 dynamic data: PLS2 data that may dynamically change frame-by-frame

PLS2 static data: PLS2 data that remains static for the duration of aframe-group

preamble signaling data: signaling data carried by the preamble symboland used to identify the basic mode of the system

preamble symbol: fixed-length pilot symbol that carries basic PLS dataand is located in the beginning of a frame

NOTE: The preamble symbol is mainly used for fast initial band scan todetect the system signal, its timing, frequency offset, and FFT-size.

reserved for future use: not defined by the present document but may bedefined in future

super-frame: set of eight frame repetition units

time interleaving block (TI block): set of cells within which timeinterleaving is carried out, corresponding to one use of the timeinterleaver memory

TI group: unit over which dynamic capacity allocation for a particularDP is carried out, made up of an integer, dynamically varying number ofXFECBLOCKs

NOTE: The TI group may be mapped directly to one frame or may be mappedto multiple frames. It may contain one or more TI blocks.

Type 1 DP: DP of a frame where all DPs are mapped into the frame in TDMfashion

Type 2 DP: DP of a frame where all DPs are mapped into the frame in FDMfashion

XFECBLOCK: set of Ncells cells carrying all the bits of one LDPCFECBLOCK

FIG. 1 illustrates a structure of an apparatus for transmittingbroadcast signals for future broadcast services according to anembodiment of the present invention.

The apparatus for transmitting broadcast signals for future broadcastservices according to an embodiment of the present invention can includean input formatting block 1000, a BICM (Bit interleaved coding &modulation) block 1010, a frame structure block 1020, an OFDM(Orthogonal Frequency Division Multiplexing) generation block 1030 and asignaling generation block 1040. A description will be given of theoperation of each module of the apparatus for transmitting broadcastsignals.

IP stream/packets and MPEG2-TS are the main input formats, other streamtypes are handled as General Streams. In addition to these data inputs,Management Information is input to control the scheduling and allocationof the corresponding bandwidth for each input stream. One or multiple TSstream(s), IP stream(s) and/or General Stream(s) inputs aresimultaneously allowed.

The input formatting block 1000 can demultiplex each input stream intoone or multiple data pipe(s), to each of which an independent coding andmodulation is applied. The data pipe (DP) is the basic unit forrobustness control, thereby affecting quality-of-service (QoS). One ormultiple service(s) or service component(s) can be carried by a singleDP. Details of operations of the input formatting block 1000 will bedescribed later.

The data pipe is a logical channel in the physical layer that carriesservice data or related metadata, which may carry one or multipleservice(s) or service component(s).

Also, the data pipe unit: a basic unit for allocating data cells to a DPin a frame.

In the BICM block 1010, parity data is added for error correction andthe encoded bit streams are mapped to complex-value constellationsymbols. The symbols are interleaved across a specific interleavingdepth that is used for the corresponding DP. For the advanced profile,MIMO encoding is performed in the BICM block 1010 and the additionaldata path is added at the output for MIMO transmission. Details ofoperations of the BICM block 1010 will be described later.

The Frame Building block 1020 can map the data cells of the input DPsinto the OFDM symbols within a frame. After mapping, the frequencyinterleaving is used for frequency-domain diversity, especially tocombat frequency-selective fading channels. Details of operations of theFrame Building block 1020 will be described later.

After inserting a preamble at the beginning of each frame, the OFDMGeneration block 1030 can apply conventional OFDM modulation having acyclic prefix as guard interval. For antenna space diversity, adistributed MISO scheme is applied across the transmitters. In addition,a Peak-to-Average Power Reduction (PAPR) scheme is performed in the timedomain. For flexible network planning, this proposal provides a set ofvarious FFT sizes, guard interval lengths and corresponding pilotpatterns. Details of operations of the OFDM Generation block 1030 willbe described later.

The Signaling Generation block 1040 can create physical layer signalinginformation used for the operation of each functional block. Thissignaling information is also transmitted so that the services ofinterest are properly recovered at the receiver side. Details ofoperations of the Signaling Generation block 1040 will be describedlater.

FIGS. 2, 3 and 4 illustrate the input formatting block 1000 according toembodiments of the present invention. A description will be given ofeach figure.

FIG. 2 illustrates an input formatting block according to one embodimentof the present invention. FIG. 2 shows an input formatting module whenthe input signal is a single input stream.

The input formatting block illustrated in FIG. 2 corresponds to anembodiment of the input formatting block 1000 described with referenceto FIG. 1.

The input to the physical layer may be composed of one or multiple datastreams. Each data stream is carried by one DP. The mode adaptationmodules slice the incoming data stream into data fields of the basebandframe (BBF). The system supports three types of input data streams:MPEG2-TS, Internet protocol (IP) and Generic stream (GS). MPEG2-TS ischaracterized by fixed length (188 byte) packets with the first bytebeing a sync-byte (0x47). An IP stream is composed of variable length IPdatagram packets, as signaled within IP packet headers. The systemsupports both IPv4 and IPv6 for the IP stream. GS may be composed ofvariable length packets or constant length packets, signaled withinencapsulation packet headers.

(a) shows a mode adaptation block 2000 and a stream adaptation 2010 forsignal DP and (b) shows a PLS generation block 2020 and a PLS scrambler2030 for generating and processing PLS data. A description will be givenof the operation of each block.

The Input Stream Splitter splits the input TS, IP, GS streams intomultiple service or service component (audio, video, etc.) streams. Themode adaptation module 2010 is comprised of a CRC Encoder, BB (baseband)Frame Slicer, and BB Frame Header Insertion block.

The CRC Encoder provides three kinds of CRC encoding for error detectionat the user packet (UP) level, i.e., CRC-8, CRC-16, and CRC-32. Thecomputed CRC bytes are appended after the UP. CRC-8 is used for TSstream and CRC-32 for IP stream. If the GS stream doesn't provide theCRC encoding, the proposed CRC encoding should be applied.

BB Frame Slicer maps the input into an internal logical-bit format. Thefirst received bit is defined to be the MSB. The BB Frame Slicerallocates a number of input bits equal to the available data fieldcapacity. To allocate a number of input bits equal to the BBF payload,the UP packet stream is sliced to fit the data field of BBF.

BB Frame Header Insertion block can insert fixed length BBF header of 2bytes is inserted in front of the BB Frame. The BBF header is composedof STUFFI (1 bit), SYNCD (13 bits), and RFU (2 bits). In addition to thefixed 2-Byte BBF header, BBF can have an extension field (1 or 3 bytes)at the end of the 2-byte BBF header.

The stream adaptation 2010 is comprised of stuffing insertion block andBB scrambler.

The stuffing insertion block can insert stuffing field into a payload ofa BB frame. If the input data to the stream adaptation is sufficient tofill a BB-Frame, STUFFI is set to ‘0’ and the BBF has no stuffing field.Otherwise STUFFI is set to ‘1’ and the stuffing field is insertedimmediately after the BBF header. The stuffing field comprises two bytesof the stuffing field header and a variable size of stuffing data.

The BB scrambler scrambles complete BBF for energy dispersal. Thescrambling sequence is synchronous with the BBF. The scrambling sequenceis generated by the feed-back shift register.

The PLS generation block 2020 can generate physical layer signaling(PLS) data. The PLS provides the receiver with a means to accessphysical layer DPs. The PLS data consists of PLS1 data and PLS2 data.

The PLS1 data is a first set of PLS data carried in the FSS symbols inthe frame having a fixed size, coding and modulation, which carriesbasic information about the system as well as the parameters needed todecode the PLS2 data. The PLS1 data provides basic transmissionparameters including parameters required to enable the reception anddecoding of the PLS2 data. Also, the PLS1 data remains constant for theduration of a frame-group.

The PLS2 data is a second set of PLS data transmitted in the FSS symbol,which carries more detailed PLS data about the system and the DPs. ThePLS2 contains parameters that provide sufficient information for thereceiver to decode the desired DP. The PLS2 signaling further consistsof two types of parameters, PLS2 Static data (PLS2-STAT data) and PLS2dynamic data (PLS2-DYN data). The PLS2 Static data is PLS2 data thatremains static for the duration of a frame-group and the PLS2 dynamicdata is PLS2 data that may dynamically change frame-by-frame.

Details of the PLS data will be described later.

The PLS scrambler 2030 can scramble the generated PLS data for energydispersal.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 3 illustrates an input formatting block according to anotherembodiment of the present invention.

The input formatting block illustrated in FIG. 3 corresponds to anembodiment of the input formatting block 1000 described with referenceto FIG. 1.

FIG. 3 shows a mode adaptation block of the input formatting block whenthe input signal corresponds to multiple input streams.

The mode adaptation block of the input formatting block for processingthe multiple input streams can independently process the multiple inputstreams.

Referring to FIG. 3, the mode adaptation block for respectivelyprocessing the multiple input streams can include an input streamsplitter 3000, an input stream synchronizer 3010, a compensating delayblock 3020, a null packet deletion block 3030, a head compression block3040, a CRC encoder 3050, a BB frame slicer 3060 and a BB headerinsertion block 3070. Description will be given of each block of themode adaptation block.

Operations of the CRC encoder 3050, BB frame slicer 3060 and BB headerinsertion block 3070 correspond to those of the CRC encoder, BB frameslicer and BB header insertion block described with reference to FIG. 2and thus description thereof is omitted.

The input stream splitter 3000 can split the input TS, IP, GS streamsinto multiple service or service component (audio, video, etc.) streams.

The input stream synchronizer 3010 may be referred as ISSY. The ISSY canprovide suitable means to guarantee Constant Bit Rate (CBR) and constantend-to-end transmission delay for any input data format. The ISSY isalways used for the case of multiple DPs carrying TS, and optionallyused for multiple DPs carrying GS streams.

The compensating delay block 3020 can delay the split TS packet streamfollowing the insertion of ISSY information to allow a TS packetrecombining mechanism without requiring additional memory in thereceiver.

The null packet deletion block 3030, is used only for the TS inputstream case. Some TS input streams or split TS streams may have a largenumber of null-packets present in order to accommodate VBR (variablebit-rate) services in a CBR TS stream. In this case, in order to avoidunnecessary transmission overhead, null-packets can be identified andnot transmitted. In the receiver, removed null-packets can bere-inserted in the exact place where they were originally by referenceto a deleted null-packet (DNP) counter that is inserted in thetransmission, thus guaranteeing constant bit-rate and avoiding the needfor time-stamp (PCR) updating.

The head compression block 3040 can provide packet header compression toincrease transmission efficiency for TS or IP input streams. Because thereceiver can have a priori information on certain parts of the header,this known information can be deleted in the transmitter.

For Transport Stream, the receiver has a-priori information about thesync-byte configuration (0x47) and the packet length (188 Byte). If theinput TS stream carries content that has only one PID, i.e., for onlyone service component (video, audio, etc.) or service sub-component (SVCbase layer, SVC enhancement layer, MVC base view or MVC dependentviews), TS packet header compression can be applied (optionally) to theTransport Stream. IP packet header compression is used optionally if theinput steam is an IP stream.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 4 illustrates an input formatting block according to anotherembodiment of the present invention.

The input formatting block illustrated in FIG. 4 corresponds to anembodiment of the input formatting block 1000 described with referenceto FIG. 1.

FIG. 4 illustrates a stream adaptation block of the input formattingmodule when the input signal corresponds to multiple input streams.

Referring to FIG. 4, the mode adaptation block for respectivelyprocessing the multiple input streams can include a scheduler 4000, an1-Frame delay block 4010, a stuffing insertion block 4020, an in-bandsignaling 4030, a BB Frame scrambler 4040, a PLS generation block 4050and a PLS scrambler 4060. Description will be given of each block of thestream adaptation block.

Operations of the stuffing insertion block 4020, the BB Frame scrambler4040, the PLS generation block 4050 and the PLS scrambler 4060correspond to those of the stuffing insertion block, BB scrambler, PLSgeneration block and the PLS scrambler described with reference to FIG.2 and thus description thereof is omitted.

The scheduler 4000 can determine the overall cell allocation across theentire frame from the amount of FECBLOCKs of each DP. Including theallocation for PLS, EAC and FIC, the scheduler generate the values ofPLS2-DYN data, which is transmitted as in-band signaling or PLS cell inFSS of the frame. Details of FECBLOCK, EAC and FIC will be describedlater.

The 1-Frame delay block 4010 can delay the input data by onetransmission frame such that scheduling information about the next framecan be transmitted through the current frame for in-band signalinginformation to be inserted into the DPs.

The in-band signaling 4030 can insert un-delayed part of the PLS2 datainto a DP of a frame.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 5 illustrates a BICM block according to an embodiment of thepresent invention.

The BICM block illustrated in FIG. 5 corresponds to an embodiment of theBICM block 1010 described with reference to FIG. 1.

As described above, the apparatus for transmitting broadcast signals forfuture broadcast services according to an embodiment of the presentinvention can provide a terrestrial broadcast service, mobile broadcastservice, UHDTV service, etc.

Since QoS (quality of service) depends on characteristics of a serviceprovided by the apparatus for transmitting broadcast signals for futurebroadcast services according to an embodiment of the present invention,data corresponding to respective services needs to be processed throughdifferent schemes. Accordingly, the a BICM block according to anembodiment of the present invention can independently process DPs inputthereto by independently applying SISO, MISO and MIMO schemes to thedata pipes respectively corresponding to data paths. Consequently, theapparatus for transmitting broadcast signals for future broadcastservices according to an embodiment of the present invention can controlQoS for each service or service component transmitted through each DP.

(a) shows the BICM block shared by the base profile and the handheldprofile and (b) shows the BICM block of the advanced profile.

The BICM block shared by the base profile and the handheld profile andthe BICM block of the advanced profile can include plural processingblocks for processing each DP.

A description will be given of each processing block of the BICM blockfor the base profile and the handheld profile and the BICM block for theadvanced profile.

A processing block 5000 of the BICM block for the base profile and thehandheld profile can include a Data FEC encoder 5010, a bit interleaver5020, a constellation mapper 5030, an SSD (Signal Space Diversity)encoding block 5040 and a time interleaver 5050.

The Data FEC encoder 5010 can perform the FEC encoding on the input BBFto generate FECBLOCK procedure using outer coding (BCH), and innercoding (LDPC). The outer coding (BCH) is optional coding method. Detailsof operations of the Data FEC encoder 5010 will be described later.

The bit interleaver 5020 can interleave outputs of the Data FEC encoder5010 to achieve optimized performance with combination of the LDPC codesand modulation scheme while providing an efficiently implementablestructure. Details of operations of the bit interleaver 5020 will bedescribed later.

The constellation mapper 5030 can modulate each cell word from the bitinterleaver 5020 in the base and the handheld profiles, or cell wordfrom the Cell-word demultiplexer 5010-1 in the advanced profile usingeither QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, NUQ-1024) ornon-uniform constellation (NUC-16, NUC-64, NUC-256, NUC-1024) to give apower-normalized constellation point, el. This constellation mapping isapplied only for DPs. Observe that QAM-16 and NUQs are square shaped,while NUCs have arbitrary shape. When each constellation is rotated byany multiple of 90 degrees, the rotated constellation exactly overlapswith its original one. This “rotation-sense” symmetric property makesthe capacities and the average powers of the real and imaginarycomponents equal to each other. Both NUQs and NUCs are definedspecifically for each code rate and the particular one used is signaledby the parameter DP_MOD filed in PLS2 data.

The SSD encoding block 5040 can precode cells in two (2D), three (3D),and four (4D) dimensions to increase the reception robustness underdifficult fading conditions.

The time interleaver 5050 can operates at the DP level. The parametersof time interleaving (TI) may be set differently for each DP. Details ofoperations of the time interleaver 5050 will be described later.

A processing block 5000-1 of the BICM block for the advanced profile caninclude the Data FEC encoder, bit interleaver, constellation mapper, andtime interleaver. However, the processing block 5000-1 is distinguishedfrom the processing block 5000 further includes a cell-worddemultiplexer 5010-1 and a MIMO encoding block 5020-1.

Also, the operations of the Data FEC encoder, bit interleaver,constellation mapper, and time interleaver in the processing block5000-1 correspond to those of the Data FEC encoder 5010, bit interleaver5020, constellation mapper 5030, and time interleaver 5050 described andthus description thereof is omitted.

The cell-word demultiplexer 5010-1 is used for the DP of the advancedprofile to divide the single cell-word stream into dual cell-wordstreams for MIMO processing. Details of operations of the cell-worddemultiplexer 5010-1 will be described later.

The MIMO encoding block 5020-1 can processing the output of thecell-word demultiplexer 5010-1 using MIMO encoding scheme. The MIMOencoding scheme was optimized for broadcasting signal transmission. TheMIMO technology is a promising way to get a capacity increase but itdepends on channel characteristics. Especially for broadcasting, thestrong LOS component of the channel or a difference in the receivedsignal power between two antennas caused by different signal propagationcharacteristics makes it difficult to get capacity gain from MIMO. Theproposed MIMO encoding scheme overcomes this problem using arotation-based pre-coding and phase randomization of one of the MIMOoutput signals.

MIMO encoding is intended for a 2×2 MIMO system requiring at least twoantennas at both the transmitter and the receiver. Two MIMO encodingmodes are defined in this proposal; full-rate spatial multiplexing(FR-SM) and full-rate full-diversity spatial multiplexing (FRFD-SM). TheFR-SM encoding provides capacity increase with relatively smallcomplexity increase at the receiver side while the FRFD-SM encodingprovides capacity increase and additional diversity gain with a greatcomplexity increase at the receiver side. The proposed MIMO encodingscheme has no restriction on the antenna polarity configuration.

MIMO processing is required for the advanced profile frame, which meansall DPs in the advanced profile frame are processed by the MIMO encoder.MIMO processing is applied at DP level. Pairs of the ConstellationMapper outputs NUQ (e1,i and e2,i) are fed to the input of the MIMOEncoder. Paired MIMO Encoder output (g1,i and g2,i) is transmitted bythe same carrier k and OFDM symbol 1 of their respective TX antennas.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 6 illustrates a BICM block according to another embodiment of thepresent invention.

The BICM block illustrated in FIG. 6 corresponds to an embodiment of theBICM block 1010 described with reference to FIG. 1.

FIG. 6 illustrates a BICM block for protection of physical layersignaling (PLS), emergency alert channel (EAC) and fast informationchannel (FIC). EAC is a part of a frame that carries EAS informationdata and FIC is a logical channel in a frame that carries the mappinginformation between a service and the corresponding base DP. Details ofthe EAC and FIC will be described later.

Referring to FIG. 6, the BICM block for protection of PLS, EAC and FICcan include a PLS FEC encoder 6000, a bit interleaver 6010, aconstellation mapper 6020 and time interleaver 6030.

Also, the PLS FEC encoder 6000 can include a scrambler, BCHencoding/zero insertion block, LDPC encoding block and LDPC paritypunturing block. Description will be given of each block of the BICMblock.

The PLS FEC encoder 6000 can encode the scrambled PLS 1/2 data, EAC andFIC section.

The scrambler can scramble PLS1 data and PLS2 data before BCH encodingand shortened and punctured LDPC encoding.

The BCH encoding/zero insertion block can perform outer encoding on thescrambled PLS 1/2 data using the shortened BCH code for PLS protectionand insert zero bits after the BCH encoding. For PLS1 data only, theoutput bits of the zero insertion may be permutted before LDPC encoding.

The LDPC encoding block can encode the output of the BCH encoding/zeroinsertion block using LDPC code. To generate a complete coded block,Cldpc, parity bits, Pldpc are encoded systematically from eachzero-inserted PLS information block, Ildpc and appended after it.C _(ldpc) =[I _(ldpc) P _(ldpc) ]=[i ₀ ,i ₁ , . . . ,i _(K) _(ldpc) ₋₁,p ₀ ,p ₁ , . . . p _(N) _(ldpc) _(-K) _(ldpc) ₋₁]  [Math figure 1]

The LDPC code parameters for PLS1 and PLS2 are as following table 4.

TABLE 4 Signaling Kldpc code Type Ksig Kbch Nbch_parity (=Nbch) NldpcNldpc_parity rate Qldpc PLS1 342 1020 60 1080 4320 3240 1/4  36 <1021PLS2 >1020 2100 2160 7200 5040 3/10 56

The LDPC parity punturing block can perform puncturing on the PLS1 dataand PLS 2 data.

When shortening is applied to the PLS1 data protection, some LDPC paritybits are punctured after LDPC encoding. Also, for the PLS2 dataprotection, the LDPC parity bits of PLS2 are punctured after LDPCencoding. These punctured bits are not transmitted.

The bit interleaver 6010 can interleave the each shortened and puncturedPLS1 data and PLS2 data.

The constellation mapper 6020 can map the bit interleaved PLS1 data andPLS2 data onto constellations.

The time interleaver 6030 can interleave the mapped PLS1 data and PLS2data.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 7 illustrates a frame building block according to one embodiment ofthe present invention.

The frame building block illustrated in FIG. 7 corresponds to anembodiment of the frame building block 1020 described with reference toFIG. 1.

Referring to FIG. 7, the frame building block can include a delaycompensation block 7000, a cell mapper 7010 and a frequency interleaver7020. Description will be given of each block of the frame buildingblock.

The delay compensation block 7000 can adjust the timing between the datapipes and the corresponding PLS data to ensure that they are co-timed atthe transmitter end. The PLS data is delayed by the same amount as datapipes are by addressing the delays of data pipes caused by the InputFormatting block and BICM block. The delay of the BICM block is mainlydue to the time interleaver 5050. In-band signaling data carriesinformation of the next TI group so that they are carried one frameahead of the DPs to be signaled. The Delay Compensating block delaysin-band signaling data accordingly.

The cell mapper 7010 can map PLS, EAC, FIC, DPs, auxiliary streams anddummy cells into the active carriers of the OFDM symbols in the frame.The basic function of the cell mapper 7010 is to map data cells producedby the TIs for each of the DPs, PLS cells, and EAC/FIC cells, if any,into arrays of active OFDM cells corresponding to each of the OFDMsymbols within a frame. Service signaling data (such as PSI (programspecific information)/SI) can be separately gathered and sent by a datapipe. The Cell Mapper operates according to the dynamic informationproduced by the scheduler and the configuration of the frame structure.Details of the frame will be described later.

The frequency interleaver 7020 can randomly interleave data cellsreceived from the cell mapper 7010 to provide frequency diversity. Also,the frequency interleaver 7020 can operate on very OFDM symbol paircomprised of two sequential OFDM symbols using a differentinterleaving-seed order to get maximum interleaving gain in a singleframe. Details of operations of the frequency interleaver 7020 will bedescribed later.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 8 illustrates an OFMD generation block according to an embodimentof the present invention.

The OFMD generation block illustrated in FIG. 8 corresponds to anembodiment of the OFMD generation block 1030 described with reference toFIG. 1.

The OFDM generation block modulates the OFDM carriers by the cellsproduced by the Frame Building block, inserts the pilots, and producesthe time domain signal for transmission. Also, this block subsequentlyinserts guard intervals, and applies PAPR (Peak-to-Average Power Radio)reduction processing to produce the final RF signal.

Referring to FIG. 8, the frame building block can include a pilot andreserved tone insertion block 8000, a 2D-eSFN encoding block 8010, anIFFT (Inverse Fast Fourier Transform) block 8020, a PAPR reduction block8030, a guard interval insertion block 8040, a preamble insertion block8050, other system insertion block 8060 and a DAC block 8070.Description will be given of each block of the frame building block.

The pilot and reserved tone insertion block 8000 can insert pilots andthe reserved tone.

Various cells within the OFDM symbol are modulated with referenceinformation, known as pilots, which have transmitted values known apriori in the receiver. The information of pilot cells is made up ofscattered pilots (SP), continual pilots (CP), edge pilots (EP), FSS(frame signaling symbol) pilots and FES (frame edge symbol) pilots. Eachpilot is transmitted at a particular boosted power level according topilot type and pilot pattern. The value of the pilot information isderived from a reference sequence, which is a series of values, one foreach transmitted carrier on any given symbol. The pilots can be used forframe synchronization, frequency synchronization, time synchronization,channel estimation, and transmission mode identification, and also canbe used to follow the phase noise.

Reference information, taken from the reference sequence, is transmittedin scattered pilot cells in every symbol except the preamble, FSS andFES of the frame. Continual pilots are inserted in every symbol of theframe. The number and location of continual pilots depends on both theFFT size and the scattered pilot pattern. The edge carriers are edgepilots in every symbol except for the preamble symbol. They are insertedin order to allow frequency interpolation up to the edge of thespectrum. FSS pilots are inserted in FSS(s) and FES pilots are insertedin FES. They are inserted in order to allow time interpolation up to theedge of the frame.

The system according to an embodiment of the present invention supportsthe SFN network, where distributed MISO scheme is optionally used tosupport very robust transmission mode. The 2D-eSFN is a distributed MISOscheme that uses multiple TX antennas, each of which is located in thedifferent transmitter site in the SFN network.

The 2D-eSFN encoding block 8010 can process a 2D-eSFN processing todistorts the phase of the signals transmitted from multipletransmitters, in order to create both time and frequency diversity inthe SFN configuration. Hence, burst errors due to low flat fading ordeep-fading for a long time can be mitigated.

The IFFT block 8020 can modulate the output from the 2D-eSFN encodingblock 8010 using OFDM modulation scheme. Any cell in the data symbolswhich has not been designated as a pilot (or as a reserved tone) carriesone of the data cells from the frequency interleaver. The cells aremapped to OFDM carriers.

The PAPR reduction block 8030 can perform a PAPR reduction on inputsignal using various PAPR reduction algorithm in the time domain.

The guard interval insertion block 8040 can insert guard intervals andthe preamble insertion block 8050 can insert preamble in front of thesignal. Details of a structure of the preamble will be described later.The other system insertion block 8060 can multiplex signals of aplurality of broadcast transmission/reception systems in the time domainsuch that data of two or more different broadcast transmission/receptionsystems providing broadcast services can be simultaneously transmittedin the same RF signal bandwidth. In this case, the two or more differentbroadcast transmission/reception systems refer to systems providingdifferent broadcast services. The different broadcast services may referto a terrestrial broadcast service, mobile broadcast service, etc. Datarelated to respective broadcast services can be transmitted throughdifferent frames.

The DAC block 8070 can convert an input digital signal into an analogsignal and output the analog signal. The signal output from the DACblock 7800 can be transmitted through multiple output antennas accordingto the physical layer profiles. A Tx antenna according to an embodimentof the present invention can have vertical or horizontal polarity.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions according to design.

FIG. 9 illustrates a structure of an apparatus for receiving broadcastsignals for future broadcast services according to an embodiment of thepresent invention.

The apparatus for receiving broadcast signals for future broadcastservices according to an embodiment of the present invention cancorrespond to the apparatus for transmitting broadcast signals forfuture broadcast services, described with reference to FIG. 1.

The apparatus for receiving broadcast signals for future broadcastservices according to an embodiment of the present invention can includea synchronization & demodulation module 9000, a frame parsing module9010, a demapping & decoding module 9020, an output processor 9030 and asignaling decoding module 9040. A description will be given of operationof each module of the apparatus for receiving broadcast signals.

The synchronization & demodulation module 9000 can receive input signalsthrough m Rx antennas, perform signal detection and synchronization withrespect to a system corresponding to the apparatus for receivingbroadcast signals and carry out demodulation corresponding to a reverseprocedure of the procedure performed by the apparatus for transmittingbroadcast signals.

The frame parsing module 9010 can parse input signal frames and extractdata through which a service selected by a user is transmitted. If theapparatus for transmitting broadcast signals performs interleaving, theframe parsing module 9010 can carry out deinterleaving corresponding toa reverse procedure of interleaving. In this case, the positions of asignal and data that need to be extracted can be obtained by decodingdata output from the signaling decoding module 9400 to restorescheduling information generated by the apparatus for transmittingbroadcast signals.

The demapping & decoding module 9020 can convert the input signals intobit domain data and then deinterleave the same as necessary. Thedemapping & decoding module 9200 can perform demapping for mappingapplied for transmission efficiency and correct an error generated on atransmission channel through decoding. In this case, the demapping &decoding module 9020 can obtain transmission parameters necessary fordemapping and decoding by decoding the data output from the signalingdecoding module 9040.

The output processor 9030 can perform reverse procedures of variouscompression/signal processing procedures which are applied by theapparatus for transmitting broadcast signals to improve transmissionefficiency. In this case, the output processor 9030 can acquirenecessary control information from data output from the signalingdecoding module 9040. The output of the output processor 9030corresponds to a signal input to the apparatus for transmittingbroadcast signals and may be MPEG-TSs, IP streams (v4 or v6) and genericstreams.

The signaling decoding module 9040 can obtain PLS information from thesignal demodulated by the synchronization & demodulation module 9000. Asdescribed above, the frame parsing module 9010, demapping & decodingmodule 9020 and output processor 9030 can execute functions thereofusing the data output from the signaling decoding module 9040.

FIG. 10 illustrates a frame structure according to an embodiment of thepresent invention.

FIG. 10 shows an example configuration of the frame types and FRUs in asuper-frame. (a) shows a super frame according to an embodiment of thepresent invention, (b) shows FRU (Frame Repetition Unit) according to anembodiment of the present invention, (c) shows frames of variable PHYprofiles in the FRU and (d) shows a structure of a frame.

A super-frame may be composed of eight FRUs. The FRU is a basicmultiplexing unit for TDM of the frames, and is repeated eight times ina super-frame.

Each frame in the FRU belongs to one of the PHY profiles, (base,handheld, advanced) or FEF. The maximum allowed number of the frames inthe FRU is four and a given PHY profile can appear any number of timesfrom zero times to four times in the FRU (e.g., base, base, handheld,advanced). PHY profile definitions can be extended using reserved valuesof the PHY_PROFILE in the preamble, if required.

The FEF part is inserted at the end of the FRU, if included. When theFEF is included in the FRU, the minimum number of FEFs is 8 in asuper-frame. It is not recommended that FEF parts be adjacent to eachother.

One frame is further divided into a number of OFDM symbols and apreamble. As shown in (d), the frame comprises a preamble, one or moreframe signaling symbols (FSS), normal data symbols and a frame edgesymbol (FES).

The preamble is a special symbol that enables fast Futurecast UTB systemsignal detection and provides a set of basic transmission parameters forefficient transmission and reception of the signal. The detaileddescription of the preamble will be will be described later.

The main purpose of the FSS(s) is to carry the PLS data. For fastsynchronization and channel estimation, and hence fast decoding of PLSdata, the FSS has more dense pilot pattern than the normal data symbol.The FES has exactly the same pilots as the FSS, which enablesfrequency-only interpolation within the FES and temporal interpolation,without extrapolation, for symbols immediately preceding the FES.

FIG. 11 illustrates a signaling hierarchy structure of the frameaccording to an embodiment of the present invention.

FIG. 11 illustrates the signaling hierarchy structure, which is splitinto three main parts: the preamble signaling data 11000, the PLS1 data11010 and the PLS2 data 11020. The purpose of the preamble, which iscarried by the preamble symbol in every frame, is to indicate thetransmission type and basic transmission parameters of that frame. ThePLS1 enables the receiver to access and decode the PLS2 data, whichcontains the parameters to access the DP of interest. The PLS2 iscarried in every frame and split into two main parts: PLS2-STAT data andPLS2-DYN data. The static and dynamic portion of PLS2 data is followedby padding, if necessary.

FIG. 12 illustrates preamble signaling data according to an embodimentof the present invention.

Preamble signaling data carries 21 bits of information that are neededto enable the receiver to access PLS data and trace DPs within the framestructure. Details of the preamble signaling data are as follows:

PHY_PROFILE: This 3-bit field indicates the PHY profile type of thecurrent frame. The mapping of different PHY profile types is given inbelow table 5.

TABLE 5 Value PHY profile 000 Base profile 001 Handheld profile 010Advanced profiled 011~110 Reserved 111 FEF

FFT_SIZE: This 2 bit field indicates the FFT size of the current framewithin a frame-group, as described in below table 6.

TABLE 6 Value FFT size 00 8K FFT 01 16K FFT 10 32K FFT 11 Reserved

GI_FRACTION: This 3 bit field indicates the guard interval fractionvalue in the current super-frame, as described in below table 7.

TABLE 7 Value GI_FRACTION 000 1/5  001 1/10 010 1/20 011 1/40 100 1/80101  1/160 110~111 Reserved

EAC_FLAG: This 1 bit field indicates whether the EAC is provided in thecurrent frame. If this field is set to ‘1’, emergency alert service(EAS) is provided in the current frame. If this field set to ‘0’, EAS isnot carried in the current frame. This field can be switched dynamicallywithin a super-frame.

PILOT_MODE: This 1-bit field indicates whether the pilot mode is mobilemode or fixed mode for the current frame in the current frame-group. Ifthis field is set to ‘0’, mobile pilot mode is used. If the field is setto ‘1’, the fixed pilot mode is used.

PAPR_FLAG: This 1-bit field indicates whether PAPR reduction is used forthe current frame in the current frame-group. If this field is set tovalue ‘1’, tone reservation is used for PAPR reduction. If this field isset to ‘0’, PAPR reduction is not used.

FRU_CONFIGURE: This 3-bit field indicates the PHY profile typeconfigurations of the frame repetition units (FRU) that are present inthe current super-frame. All profile types conveyed in the currentsuper-frame are identified in this field in all preambles in the currentsuper-frame. The 3-bit field has a different definition for eachprofile, as show in below table 8.

TABLE 8 Current Current Current Current PHY_PROFILE = ‘000’ PHY_PROFILE= ‘001’ PHY_PROFILE = ‘010’ PHY_PROFILE = ‘111’ (base) (handheld)(advanced) (FEF) FRU_CONFIGURE = 000 Only base Only handheld Onlyadvanced Only FEF profile present profile present profile presentpresent FRU_CONFIGURE = 1XX Handheld Base Base Base profile presentprofile present profile present profile present FRU_CONFIGURE = X1XAdvanced Advanced Handheld Handheld profile present profile presentprofile present profile present FRU_CONFIGURE = XX1 FEF FEF FEF Advancedpresent present present profile present

RESERVED: This 7-bit field is reserved for future use.

FIG. 13 illustrates PLS1 data according to an embodiment of the presentinvention.

PLS1 data provides basic transmission parameters including parametersrequired to enable the reception and decoding of the PLS2. As abovementioned, the PLS1 data remain unchanged for the entire duration of oneframe-group. The detailed definition of the signaling fields of the PLS1data are as follows:

PREAMBLE_DATA: This 20-bit field is a copy of the preamble signalingdata excluding the EAC_FLAG.

NUM_FRAME_FRU: This 2-bit field indicates the number of the frames perFRU.

PAYLOAD_TYPE: This 3-bit field indicates the format of the payload datacarried in the frame-group. PAYLOAD_TYPE is signaled as shown in table9.

TABLE 9 Value Payload type 1XX TS stream is transmitted X1X IP stream istransmitted XX1 GS stream is transmitted

NUM_FSS: This 2-bit field indicates the number of FSS symbols in thecurrent frame.

SYSTEM_VERSION: This 8-bit field indicates the version of thetransmitted signal format. The SYSTEM_VERSION is divided into two 4-bitfields, which are a major version and a minor version.

Major version: The MSB four bits of SYSTEM_VERSION field indicate majorversion information. A change in the major version field indicates anon-backward-compatible change. The default value is ‘0000’. For theversion described in this standard, the value is set to ‘0000’.

Minor version: The LSB four bits of SYSTEM_VERSION field indicate minorversion information. A change in the minor version field isbackward-compatible.

CELL_ID: This is a 16-bit field which uniquely identifies a geographiccell in an ATSC network. An ATSC cell coverage area may consist of oneor more frequencies, depending on the number of frequencies used perFuturecast UTB system. If the value of the CELL_ID is not known orunspecified, this field is set to ‘0’.

NETWORK_ID: This is a 16-bit field which uniquely identifies the currentATSC network.

SYSTEM_ID: This 16-bit field uniquely identifies the Futurecast UTBsystem within the ATSC network. The Futurecast UTB system is theterrestrial broadcast system whose input is one or more input streams(TS, IP, GS) and whose output is an RF signal. The Futurecast UTB systemcarries one or more PHY profiles and FEF, if any. The same FuturecastUTB system may carry different input streams and use different RFfrequencies in different geographical areas, allowing local serviceinsertion. The frame structure and scheduling is controlled in one placeand is identical for all transmissions within a Futurecast UTB system.One or more Futurecast UTB systems may have the same SYSTEM_ID meaningthat they all have the same physical layer structure and configuration.

The following loop consists of FRU_PHY_PROFILE, FRU_FRAME_LENGTH,FRU_GI_FRACTION, and RESERVED which are used to indicate the FRUconfiguration and the length of each frame type. The loop size is fixedso that four PHY profiles (including a FEF) are signaled within the FRU.If NUM_FRAME_FRU is less than 4, the unused fields are filled withzeros.

FRU_PHY_PROFILE: This 3-bit field indicates the PHY profile type of the(i+1)th (i is the loop index) frame of the associated FRU. This fielduses the same signaling format as shown in the table 8.

FRU_FRAME_LENGTH: This 2-bit field indicates the length of the (i+1)thframe of the associated FRU. Using FRU_FRAME_LENGTH together withFRU_GI_FRACTION, the exact value of the frame duration can be obtained.

FRU_GI_FRACTION: This 3-bit field indicates the guard interval fractionvalue of the (i+1)th frame of the associated FRU. FRU_GI_FRACTION issignaled according to the table 7.

RESERVED: This 4-bit field is reserved for future use.

The following fields provide parameters for decoding the PLS2 data.

PLS2_FEC_TYPE: This 2-bit field indicates the FEC type used by the PLS2protection. The FEC type is signaled according to table 10. The detailsof the LDPC codes will be described later.

TABLE 10 Content PLS2 FEC type 00 4K-1/4 and 7K-3/10 LDPC codes 01~11Reserved

PLS2_MOD: This 3-bit field indicates the modulation type used by thePLS2. The modulation type is signaled according to table 11.

TABLE 11 Value PLS2_MODE 000 BPSK 001 QPSK 010 QAM-16 011 NUQ-64 100~111Reserved

PLS2_SIZE_CELL: This 15-bit field indicates Ctotal_partial_block, thesize (specified as the number of QAM cells) of the collection of fullcoded blocks for PLS2 that is carried in the current frame-group. Thisvalue is constant during the entire duration of the current frame-group.

PLS2_STAT_SIZE_BIT: This 14-bit field indicates the size, in bits, ofthe PLS2-STAT for the current frame-group. This value is constant duringthe entire duration of the current frame-group.

PLS2_DYN_SIZE_BIT: This 14-bit field indicates the size, in bits, of thePLS2-DYN for the current frame-group. This value is constant during theentire duration of the current frame-group.

PLS2_REP_FLAG: This 1-bit flag indicates whether the PLS2 repetitionmode is used in the current frame-group. When this field is set to value‘1’, the PLS2 repetition mode is activated. When this field is set tovalue ‘0’, the PLS2 repetition mode is deactivated.

PLS2_REP_SIZE_CELL: This 15-bit field indicates Ctotal_partial_block,the size (specified as the number of QAM cells) of the collection ofpartial coded blocks for PLS2 carried in every frame of the currentframe-group, when PLS2 repetition is used. If repetition is not used,the value of this field is equal to 0. This value is constant during theentire duration of the current frame-group.

PLS2_NEXT_FEC_TYPE: This 2-bit field indicates the FEC type used forPLS2 that is carried in every frame of the next frame-group. The FECtype is signaled according to the table 10.

PLS2_NEXT_MOD: This 3-bit field indicates the modulation type used forPLS2 that is carried in every frame of the next frame-group. Themodulation type is signaled according to the table 11.

PLS2_NEXT_REP_FLAG: This 1-bit flag indicates whether the PLS2repetition mode is used in the next frame-group. When this field is setto value ‘1’, the PLS2 repetition mode is activated. When this field isset to value ‘0’, the PLS2 repetition mode is deactivated.

PLS 2_NEXT_REP_SIZE_CELL: This 15-bit field indicates Ctotal full block,The size (specified as the number of QAM cells) of the collection offull coded blocks for PLS2 that is carried in every frame of the nextframe-group, when

PLS2 repetition is used. If repetition is not used in the nextframe-group, the value of this field is equal to 0. This value isconstant during the entire duration of the current frame-group.

PLS2_NEXT_REP_STAT_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-STAT for the next frame-group. This value is constantin the current frame-group.

PLS2_NEXT_REP_DYN_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-DYN for the next frame-group. This value is constantin the current frame-group.

PLS2_AP_MODE: This 2-bit field indicates whether additional parity isprovided for PLS2 in the current frame-group. This value is constantduring the entire duration of the current frame-group. The below table12 gives the values of this field. When this field is set to ‘00’,additional parity is not used for the PLS2 in the current frame-group.

TABLE 12 Value PLS2-AP mode 00 AP is not provided 01 AP1 mode 10~11Reserved

PLS2_AP_SIZE_CELL: This 15-bit field indicates the size (specified asthe number of QAM cells) of the additional parity bits of the PLS2. Thisvalue is constant during the entire duration of the current frame-group.

PLS2_NEXT_AP_MODE: This 2-bit field indicates whether additional parityis provided for PLS2 signaling in every frame of next frame-group. Thisvalue is constant during the entire duration of the current frame-group.The table 12 defines the values of this field

PLS2_NEXT_AP_SIZE_CELL: This 15-bit field indicates the size (specifiedas the number of QAM cells) of the additional parity bits of the PLS2 inevery frame of the next frame-group. This value is constant during theentire duration of the current frame-group.

RESERVED: This 32-bit field is reserved for future use.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS1 signaling.

FIG. 14 illustrates PLS2 data according to an embodiment of the presentinvention.

FIG. 14 illustrates PLS2-STAT data of the PLS2 data. The PLS2-STAT dataare the same within a frame-group, while the PLS2-DYN data provideinformation that is specific for the current frame.

The details of fields of the PLS2-STAT data are as follows:

FIC_FLAG: This 1-bit field indicates whether the FIC is used in thecurrent frame-group. If this field is set to ‘1’, the FIC is provided inthe current frame. If this field set to ‘0’, the FIC is not carried inthe current frame. This value is constant during the entire duration ofthe current frame-group.

AUX_FLAG: This 1-bit field indicates whether the auxiliary stream(s) isused in the current frame-group. If this field is set to ‘1’, theauxiliary stream is provided in the current frame. If this field set to‘0’, the auxiliary stream is not carried in the current frame. Thisvalue is constant during the entire duration of current frame-group.

NUM_DP: This 6-bit field indicates the number of DPs carried within thecurrent frame. The value of this field ranges from 1 to 64, and thenumber of DPs is NUM_DP+1.

DP_ID: This 6-bit field identifies uniquely a DP within a PHY profile.

DP_TYPE: This 3-bit field indicates the type of the DP. This is signaledaccording to the below table 13.

TABLE 13 Value DP Type 000 DP Type 1 001 DP Type 2 010~111 reserved

DP_GROUP_ID: This 8-bit field identifies the DP group with which thecurrent DP is associated. This can be used by a receiver to access theDPs of the service components associated with a particular service,which will have the same DP_GROUP_ID.

BASE_DP_ID: This 6-bit field indicates the DP carrying service signalingdata (such as PSI/SI) used in the Management layer. The DP indicated byBASE_DP_ID may be either a normal DP carrying the service signaling dataalong with the service data or a dedicated DP carrying only the servicesignaling data

DP_FEC_TYPE: This 2-bit field indicates the FEC type used by theassociated DP. The FEC type is signaled according to the below table 14.

TABLE 14 Value FEC_TYPE 00 16K LDPC 01 64K LDPC 10~11 Reserved

DP_COD: This 4-bit field indicates the code rate used by the associatedDP. The code rate is signaled according to the below table 15.

TABLE 15 Value Code rate 0000 5/15 0001 6/15 0010 7/15 0011 8/15 01009/15 0101 10/15  0110 11/15  0111 12/15  1000 13/15  1001~1111 Reserved

DP_MOD: This 4-bit field indicates the modulation used by the associatedDP. The modulation is signaled according to the below table 16.

TABLE 16 Value Modulation 0000 QPSK 0001 QAM-16 0010 NUQ-64 0011 NUQ-2560100 NUQ-1024 0101 NUC-16 0110 NUC-64 0111 NUC-256 1000 NUC-10241001~1111 reserved

DP_SSD_FLAG: This 1-bit field indicates whether the SSD mode is used inthe associated DP. If this field is set to value ‘1’, SSD is used. Ifthis field is set to value ‘0’, SSD is not used.

The following field appears only if PHY_PROFILE is equal to ‘010’, whichindicates the advanced profile:

DP_MIMO: This 3-bit field indicates which type of MIMO encoding processis applied to the associated DP. The type of MIMO encoding process issignaled according to the table 17.

TABLE 17 Value MIMO encoding 000 FR-SM 001 FRFD-SM 010~111 reserved

DP_TI_TYPE: This 1-bit field indicates the type of time-interleaving. Avalue of ‘0’ indicates that one TI group corresponds to one frame andcontains one or more TI-blocks. A value of ‘1’ indicates that one TIgroup is carried in more than one frame and contains only one TI-block.

DP_TI_LENGTH: The use of this 2-bit field (the allowed values are only1, 2, 4, 8) is determined by the values set within the DP_TI_TYPE fieldas follows:

If the DP_TI_TYPE is set to the value ‘1’, this field indicates PI, thenumber of the frames to which each TI group is mapped, and there is oneTI-block per TI group (NTI=1). The allowed PI values with 2-bit fieldare defined in the below table 18.

If the DP_TI_TYPE is set to the value ‘0’, this field indicates thenumber of TI-blocks NTI per TI group, and there is one TI group perframe (Pi=1). The allowed PI values with 2-bit field are defined in thebelow table 18.

TABLE 18 2-bit field PI NTI 00 1 1 01 2 2 10 4 3 11 8 4

DP_FRAME_INTERVAL: This 2-bit field indicates the frame interval (IJUMP)within the frame-group for the associated DP and the allowed values are1, 2, 4, 8 (the corresponding 2-bit field is ‘00’, ‘01’, ‘10’, or ‘11’,respectively). For DPs that do not appear every frame of theframe-group, the value of this field is equal to the interval betweensuccessive frames. For example, if a DP appears on the frames 1, 5, 9,13, etc., this field is set to ‘4’. For DPs that appear in every frame,this field is set to ‘1’.

DP_TI_BYPASS: This 1-bit field determines the availability of timeinterleaver 5050. If time interleaving is not used for a DP, it is setto ‘1’. Whereas if time interleaving is used it is set to ‘0’.

DP_FIRST_FRAME_IDX: This 5-bit field indicates the index of the firstframe of the super-frame in which the current DP occurs. The value ofDP_FIRST_FRAME_IDX ranges from 0 to 31

DP_NUM_BLOCK_MAX: This 10-bit field indicates the maximum value ofDP_NUM_BLOCKS for this DP. The value of this field has the same range asDP_NUM_BLOCKS.

DP_PAYLOAD_TYPE: This 2-bit field indicates the type of the payload datacarried by the given DP. DP_PAYLOAD_TYPE is signaled according to thebelow table 19.

TABLE 19 Value Payload Type 00 TS. 01 IP 10 GS 11 reserved

DP_INBAND_MODE: This 2-bit field indicates whether the current DPcarries in-band signaling information. The in-band signaling type issignaled according to the below table 20.

TABLE 20 Value In-band mode 00 In-band signaling is not carried. 01INBAND-PLS is carried only 10 INBAND-ISSY is carried only 11 INBAND-PLSand INBAND-ISSY are carried

DP_PROTOCOL_TYPE: This 2-bit field indicates the protocol type of thepayload carried by the given DP. It is signaled according to the belowtable 21 when input payload types are selected.

TABLE 21 If If If DP_PAY- DP_PAY- DP_PAY- LOAD_TYPE LOAD_TYPE LOAD_TYPEValue Is TS Is IP Is GS 00 MPEG2-TS IPv4 (Note) 01 Reserved IPv6Reserved 10 Reserved Reserved Reserved 11 Reserved Reserved Reserved

DP_CRC_MODE: This 2-bit field indicates whether CRC encoding is used inthe Input Formatting block. The CRC mode is signaled according to thebelow table 22.

TABLE 22 Value CRC mode 00 Not used 01 CRC-8 10 CRC-16 11 CRC-32

DNP_MODE: This 2-bit field indicates the null-packet deletion mode usedby the associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). DNP_MODEis signaled according to the below table 23. If DP_PAYLOAD_TYPE is notTS (‘00’), DNP_MODE is set to the value ‘00’.

TABLE 23 Value Null-packet deletion mode 00 Not used 01 DNP-NORMAL 10DNP-OFFSET 11 reserved

ISSY_MODE: This 2-bit field indicates the ISSY mode used by theassociated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). The ISSY_MODE issignaled according to the below table 24 If DP_PAYLOAD_TYPE is not TS(‘00’), ISSY_MODE is set to the value ‘00’.

TABLE 24 Value ISSY mode 00 Not used 01 ISSY-UP 10 ISSY-BBF 11 reserved

HC_MODE_TS: This 2-bit field indicates the TS header compression modeused by the associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). TheHC_MODE_TS is signaled according to the below table 25.

TABLE 25 Value Header compression mode 00 HC_MODE_TS 1 01 HC_MODE_TS 210 HC_MODE_TS 3 11 HC_MODE_TS 4

HC_MODE_IP: This 2-bit field indicates the IP header compression modewhen DP_PAYLOAD_TYPE is set to IP (‘01’). The HC_MODE_IP is signaledaccording to the below table 26.

TABLE 26 Value Header compression mode 00 No compression 01 HC_MODE_IP 110~11 reserved

PID: This 13-bit field indicates the PID number for TS headercompression when DP_PAYLOAD_TYPE is set to TS (‘00’) and HC_MODE_TS isset to ‘01’ or ‘10’.

RESERVED: This 8-bit field is reserved for future use.

The following field appears only if FIC_FLAG is equal to ‘1’:

FIC_VERSION: This 8-bit field indicates the version number of the FIC.

FIC_LENGTH_BYTE: This 13-bit field indicates the length, in bytes, ofthe FIC.

RESERVED: This 8-bit field is reserved for future use.

The following field appears only if AUX_FLAG is equal to ‘1’:

NUM_AUX: This 4-bit field indicates the number of auxiliary streams.Zero means no auxiliary streams are used.

AUX_CONFIG_RFU: This 8-bit field is reserved for future use.

AUX_STREAM_TYPE: This 4-bit is reserved for future use for indicatingthe type of the current auxiliary stream.

AUX_PRIVATE_CONFIG: This 28-bit field is reserved for future use forsignaling auxiliary streams.

FIG. 15 illustrates PLS2 data according to another embodiment of thepresent invention.

FIG. 15 illustrates PLS2-DYN data of the PLS2 data. The values of thePLS2-DYN data may change during the duration of one frame-group, whilethe size of fields remains constant.

The details of fields of the PLS2-DYN data are as follows:

FRAME_INDEX: This 5-bit field indicates the frame index of the currentframe within the super-frame. The index of the first frame of thesuper-frame is set to ‘0’.

PLS_CHANGE_COUNTER: This 4-bit field indicates the number ofsuper-frames ahead where the configuration will change. The nextsuper-frame with changes in the configuration is indicated by the valuesignaled within this field. If this field is set to the value ‘0000’, itmeans that no scheduled change is foreseen: e.g., value ‘1’ indicatesthat there is a change in the next super-frame.

FIC_CHANGE_COUNTER: This 4-bit field indicates the number ofsuper-frames ahead where the configuration (i.e., the contents of theFIC) will change. The next super-frame with changes in the configurationis indicated by the value signaled within this field. If this field isset to the value ‘0000’, it means that no scheduled change is foreseen:e.g. value ‘0001’ indicates that there is a change in the nextsuper-frame.

RESERVED: This 16-bit field is reserved for future use.

The following fields appear in the loop over NUM_DP, which describe theparameters associated with the DP carried in the current frame.

DP_ID: This 6-bit field indicates uniquely the DP within a PHY profile.

DP_START: This 15-bit (or 13-bit) field indicates the start position ofthe first of the DPs using the DPU addressing scheme. The DP_START fieldhas differing length according to the PHY profile and FFT size as shownin the below table 27.

TABLE 27 DP_START field size PHY profile 64K 16K Base 13 bit 15 bitHandheld — 13 bit Advanced 13 bit 15 bit

DP_NUM_BLOCK: This 10-bit field indicates the number of FEC blocks inthe current TI group for the current DP. The value of DP_NUM_BLOCKranges from 0 to 1023

RESERVED: This 8-bit field is reserved for future use.

The following fields indicate the FIC parameters associated with theEAC.

EAC_FLAG: This 1-bit field indicates the existence of the EAC in thecurrent frame. This bit is the same value as the EAC_FLAG in thepreamble.

EAS_WAKE_UP_VERSION_NUM: This 8-bit field indicates the version numberof a wake-up indication.

If the EAC_FLAG field is equal to ‘1’, the following 12 bits areallocated for EAC_LENGTH_BYTE field. If the EAC_FLAG field is equal to‘0’, the following 12 bits are allocated for EAC_COUNTER.

EAC_LENGTH_BYTE: This 12-bit field indicates the length, in byte, of theEAC.

EAC_COUNTER: This 12-bit field indicates the number of the frames beforethe frame where the EAC arrives.

The following field appears only if the AUX_FLAG field is equal to ‘1’:

AUX_PRIVATE_DYN: This 48-bit field is reserved for future use forsignaling auxiliary streams. The meaning of this field depends on thevalue of AUX_STREAM_TYPE in the configurable PLS2-STAT.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS2.

FIG. 16 illustrates a logical structure of a frame according to anembodiment of the present invention.

As above mentioned, the PLS, EAC, FIC, DPs, auxiliary streams and dummycells are mapped into the active carriers of the OFDM symbols in theframe. The PLS1 and PLS2 are first mapped into one or more FSS(s). Afterthat, EAC cells, if any, are mapped immediately following the PLS field,followed next by FIC cells, if any. The DPs are mapped next after thePLS or EAC, FIC, if any. Type 1 DPs follows first, and Type 2 DPs next.The details of a type of the DP will be described later. In some case,DPs may carry some special data for EAS or service signaling data. Theauxiliary stream or streams, if any, follow the DPs, which in turn arefollowed by dummy cells. Mapping them all together in the abovementioned order, i.e. PLS, EAC, FIC, DPs, auxiliary streams and dummydata cells exactly fill the cell capacity in the frame.

FIG. 17 illustrates PLS mapping according to an embodiment of thepresent invention.

PLS cells are mapped to the active carriers of FSS(s). Depending on thenumber of cells occupied by PLS, one or more symbols are designated asFSS(s), and the number of FSS(s) N_FSS is signaled by NUM_FSS in PLS1.The FSS is a special symbol for carrying PLS cells. Since robustness andlatency are critical issues in the PLS, the FSS(s) has higher density ofpilots allowing fast synchronization and frequency-only interpolationwithin the FSS.

PLS cells are mapped to active carriers of the NFSS FSS(s) in a top-downmanner as shown in an example in FIG. 17. The PLS1 cells are mappedfirst from the first cell of the first FSS in an increasing order of thecell index. The PLS2 cells follow immediately after the last cell of thePLS1 and mapping continues downward until the last cell index of thefirst FSS. If the total number of required PLS cells exceeds the numberof active carriers of one FSS, mapping proceeds to the next FSS andcontinues in exactly the same manner as the first FSS.

After PLS mapping is completed, DPs are carried next. If EAC, FIC orboth are present in the current frame, they are placed between PLS and“normal” DPs.

FIG. 18 illustrates EAC mapping according to an embodiment of thepresent invention.

EAC is a dedicated channel for carrying EAS messages and links to theDPs for EAS. EAS support is provided but EAC itself may or may not bepresent in every frame. EAC, if any, is mapped immediately after thePLS2 cells. EAC is not preceded by any of the FIC, DPs, auxiliarystreams or dummy cells other than the PLS cells. The procedure ofmapping the EAC cells is exactly the same as that of the PLS.

The EAC cells are mapped from the next cell of the PLS2 in increasingorder of the cell index as shown in the example in FIG. 18. Depending onthe EAS message size, EAC cells may occupy a few symbols, as shown inFIG. 18.

EAC cells follow immediately after the last cell of the PLS2, andmapping continues downward until the last cell index of the last FSS. Ifthe total number of required EAC cells exceeds the number of remainingactive carriers of the last FSS mapping proceeds to the next symbol andcontinues in exactly the same manner as FSS(s). The next symbol formapping in this case is the normal data symbol, which has more activecarriers than a FSS.

After EAC mapping is completed, the FIC is carried next, if any exists.If FIC is not transmitted (as signaled in the PLS2 field), DPs followimmediately after the last cell of the EAC.

FIG. 19 illustrates FIC mapping according to an embodiment of thepresent invention.

(a) shows an example mapping of FIC cell without EAC and (b) shows anexample mapping of FIC cell with EAC.

FIC is a dedicated channel for carrying cross-layer information toenable fast service acquisition and channel scanning. This informationprimarily includes channel binding information between DPs and theservices of each broadcaster. For fast scan, a receiver can decode FICand obtain information such as broadcaster ID, number of services, andBASE_DP_ID. For fast service acquisition, in addition to FIC, base DPcan be decoded using BASE_DP_ID. Other than the content it carries, abase DP is encoded and mapped to a frame in exactly the same way as anormal DP. Therefore, no additional description is required for a baseDP. The FIC data is generated and consumed in the Management Layer. Thecontent of FIC data is as described in the Management Layerspecification.

The FIC data is optional and the use of FIC is signaled by the FIC_FLAGparameter in the static part of the PLS2 . If FIC is used, FIC_FLAG isset to ‘1’ and the signaling field for FIC is defined in the static partof PLS2 . Signaled in this field are FIC_VERSION, and FIC_LENGTH_BYTE.FIC uses the same modulation, coding and time interleaving parameters asPLS2. FIC shares the same signaling parameters such as PLS2_MOD andPLS2_FEC. FIC data, if any, is mapped immediately after PLS2 or EAC ifany. FIC is not preceded by any normal DPs, auxiliary streams or dummycells. The method of mapping FIC cells is exactly the same as that ofEAC which is again the same as PLS.

Without EAC after PLS, FIC cells are mapped from the next cell of thePLS2 in an increasing order of the cell index as shown in an example in(a). Depending on the FIC data size, FIC cells may be mapped over a fewsymbols, as shown in (b).

FIC cells follow immediately after the last cell of the PLS2, andmapping continues downward until the last cell index of the last FSS. Ifthe total number of required

FIC cells exceeds the number of remaining active carriers of the lastFSS, mapping proceeds to the next symbol and continues in exactly thesame manner as FSS(s). The next symbol for mapping in this case is thenormal data symbol which has more active carriers than a FSS.

If EAS messages are transmitted in the current frame, EAC precedes FIC,and FIC cells are mapped from the next cell of the EAC in an increasingorder of the cell index as shown in (b).

After FIC mapping is completed, one or more DPs are mapped, followed byauxiliary streams, if any, and dummy cells.

FIG. 20 illustrates a type of DP according to an embodiment of thepresent invention.

shows type 1 DP and (b) shows type 2 DP.

After the preceding channels, i.e., PLS, EAC and FIC, are mapped, cellsof the DPs are mapped. A DP is categorized into one of two typesaccording to mapping method:

Type 1 DP: DP is mapped by TDM

Type 2 DP: DP is mapped by FDM

The type of DP is indicated by DP_TYPE field in the static part of PLS2. FIG. 20 illustrates the mapping orders of Type 1 DPs and Type 2 DPs.Type 1 DPs are first mapped in the increasing order of cell index, andthen after reaching the last cell index, the symbol index is increasedby one. Within the next symbol, the DP continues to be mapped in theincreasing order of cell index starting from p=0. With a number of DPsmapped together in one frame, each of the Type 1 DPs are grouped intime, similar to TDM multiplexing of DPs.

Type 2 DPs are first mapped in the increasing order of symbol index, andthen after reaching the last OFDM symbol of the frame, the cell indexincreases by one and the symbol index rolls back to the first availablesymbol and then increases from that symbol index. After mapping a numberof DPs together in one frame, each of the Type 2 DPs are grouped infrequency together, similar to FDM multiplexing of DPs.

Type 1 DPs and Type 2 DPs can coexist in a frame if needed with onerestriction; Type 1 DPs always precede Type 2 DPs. The total number ofOFDM cells carrying Type 1 and Type 2 DPs cannot exceed the total numberof OFDM cells available for transmission of DPs:D _(DP1) +D _(DP2) ≦D _(DP)  [Math figure 2]

where DDP1 is the number of OFDM cells occupied by Type 1 DPs, DDP2 isthe number of cells occupied by Type 2 DPs. Since PLS, EAC, FIC are allmapped in the same way as Type 1 DP, they all follow “Type 1 mappingrule”. Hence, overall, Type 1 mapping always precedes Type 2 mapping.

FIG. 21 illustrates DP mapping according to an embodiment of the presentinvention.

shows an addressing of OFDM cells for mapping type 1 DPs and (b) showsan addressing of OFDM cells for mapping for type 2 DPs.

Addressing of OFDM cells for mapping Type 1 DPs (0, . . . , DDP1-1) isdefined for the active data cells of Type 1 DPs.

The addressing scheme defines the order in which the cells from the TIsfor each of the Type 1 DPs are allocated to the active data cells. It isalso used to signal the locations of the DPs in the dynamic part of thePLS2.

Without EAC and FIC, address 0 refers to the cell immediately followingthe last cell carrying PLS in the last FSS. If EAC is transmitted andFIC is not in the corresponding frame, address 0 refers to the cellimmediately following the last cell carrying EAC. If FIC is transmittedin the corresponding frame, address 0 refers to the cell immediatelyfollowing the last cell carrying FIC. Address 0 for Type 1 DPs can becalculated considering two different cases as shown in (a). In theexample in (a), PLS, EAC and FIC are assumed to be all transmitted.Extension to the cases where either or both of EAC and FIC are omittedis straightforward. If there are remaining cells in the FSS aftermapping all the cells up to FIC as shown on the left side of (a).

Addressing of OFDM cells for mapping Type 2 DPs (0, . . . , DDP2-1) isdefined for the active data cells of Type 2 DPs. The addressing schemedefines the order in which the cells from the TIs for each of the Type 2DPs are allocated to the active data cells. It is also used to signalthe locations of the DPs in the dynamic part of the PLS2.

Three slightly different cases are possible as shown in (b). For thefirst case shown on the left side of (b), cells in the last FSS areavailable for Type 2 DP mapping. For the second case shown in themiddle, FIC occupies cells of a normal symbol, but the number of FICcells on that symbol is not larger than CFSS. The third case, shown onthe right side in (b), is the same as the second case except that thenumber of FIC cells mapped on that symbol exceeds CFSS.

The extension to the case where Type 1 DP(s) precede Type 2 DP(s) isstraightforward since PLS, EAC and FIC follow the same “Type 1 mappingrule” as the Type 1 DP(s).

A data pipe unit (DPU) is a basic unit for allocating data cells to a DPin a frame.

A DPU is defined as a signaling unit for locating DPs in a frame. A CellMapper 7010 may map the cells produced by the TIs for each of the DPs. ATime interleaver 5050 outputs a series of TI-blocks and each TI-blockcomprises a variable number of XFECBLOCKs which is in turn composed of aset of cells. The number of cells in an XFECBLOCK, Ncells, is dependenton the FECBLOCK size, Nldpc, and the number of transmitted bits perconstellation symbol. A DPU is defined as the greatest common divisor ofall possible values of the number of cells in a XFECBLOCK, Ncells,supported in a given PHY profile. The length of a DPU in cells isdefined as LDPU. Since each PHY profile supports different combinationsof FECBLOCK size and a different number of bits per constellationsymbol, LDPU is defined on a PHY profile basis.

FIG. 22 illustrates an FEC structure according to an embodiment of thepresent invention.

FIG. 22 illustrates an FEC structure according to an embodiment of thepresent invention before bit interleaving. As above mentioned, Data FECencoder may perform the FEC encoding on the input BBF to generateFECBLOCK procedure using outer coding (BCH), and inner coding (LDPC).The illustrated FEC structure corresponds to the FECBLOCK. Also, theFECBLOCK and the FEC structure have same value corresponding to a lengthof LDPC codeword.

The BCH encoding is applied to each BBF (Kbch bits), and then LDPCencoding is applied to BCH-encoded BBF (Kldpc bits=Nbch bits) asillustrated in FIG. 22.

The value of Nldpc is either 64800 bits (long FECBLOCK) or 16200 bits(short FECBLOCK).

The below table 28 and table 29 show FEC encoding parameters for a longFECBLOCK and a short FECBLOCK, respectively.

TABLE 28 BCH error LDPC correction Nbch − Rate Nldpc Kldpc Kbchcapability Kbch 5/15 64800 21600 21408 12 192 6/15 25920 25728 7/1530240 30048 8/15 34560 34368 9/15 38880 38688 10/15  43200 43008 11/15 47520 47328 12/15  51840 51648 13/15  56160 55968

TABLE 29 BCH error LDPC correction Nbch − Rate Nldpc Kldpc Kbchcapability Kbch 5/15 16200 5400 5232 12 168 6/15 6480 6312 7/15 75607392 8/15 8640 8472 9/15 9720 9552 10/15  10800 10632 11/15  11880 1171212/15  12960 12792 13/15  14040 13872

The details of operations of the BCH encoding and LDPC encoding are asfollows:

A 12-error correcting BCH code is used for outer encoding of the BBF.The BCH generator polynomial for short FECBLOCK and long FECBLOCK areobtained by multiplying together all polynomials.

LDPC code is used to encode the output of the outer BCH encoding. Togenerate a completed Bldpc (FECBLOCK), Pldpc (parity bits) is encodedsystematically from each Ildpc (BCH-encoded BBF), and appended to Ildpc.The completed Bldpc (FECBLOCK) are expressed as follow Math figure.B _(ldpc) =[I _(ldpc) P _(ldpc) ]=[i ₀ ,i ₁ , . . . ,i _(K) _(ldpc) ₋₁,p ₀ ,p ₁ , . . . p _(N) _(ldpc) _(-K) _(ldpc) ₋₁]  [Math figure 3]

The parameters for long FECBLOCK and short FECBLOCK are given in theabove table 28 and 29, respectively.

The detailed procedure to calculate Nldpc−Kldpc parity bits for longFECBLOCK, is as follows:

1) Initialize the parity bits,p ₀ =p ₁ =p ₂ = . . . =p _(N) _(ldpc) _(-K) _(ldpc) ₋₁=0  [Math figure4]

2) Accumulate the first information bit—i0, at parity bit addressesspecified in the first row of an addresses of parity check matrix. Thedetails of addresses of parity check matrix will be described later. Forexample, for rate 13/15:p ₉₈₃ =p ₉₈₃ ⊕i ₀ p ₂₈₁₅ =p ₂₈₁₅ ⊕i ₀p ₄₈₃₇ =p ₄₈₃₇ ⊕i ₀ p ₄₉₈₉ =p ₄₉₈₉ ⊕i ₀p ₆₁₃₈ =p ₆₁₃₈ ⊕i ₀ p ₆₄₅₈ =p ₆₄₅₈ ⊕i ₀p ₆₉₂₁ =p ₆₉₂₁ ⊕i ₀ p ₆₉₇₄ =p ₆₉₇₄ ⊕i ₀p ₇₅₇₂ =p ₇₅₇₂ ⊕i ₀ p ₈₂₆₀ =p ₈₂₆₀ ⊕i ₀p ₈₄₉₆ =p ₈₄₉₆ ⊕i ₀  [Math figure 5]

3) For the next 359 information bits, is, s=1, 2, . . . , 359 accumulateis at parity bit addresses using following Math figure.{x+(s mod 360)×Q _(ldpc)} mod(N _(ldpc) −K _(ldpc))  [Math figure 6]

where x denotes the address of the parity bit accumulator correspondingto the first bit i0, and Qldpc is a code rate dependent constantspecified in the addresses of parity check matrix. Continuing with theexample, Qldpc=24 for rate 13/15, so for information bit i1, thefollowing operations are performed:p ₁₀₀₇ =p ₁₀₀₇ ⊕i ₁ p ₂₈₃₉ =p ₂₈₃₉ ⊕i ₁p ₄₈₆₁ =p ₄₈₆₁ ⊕i ₁ p ₅₀₁₃ =p ₅₀₁₃ ⊕i ₁p ₆₁₆₂ =p ₆₁₆₂ ⊕i ₁ p ₆₄₈₂ =p ₆₄₈₂ ⊕i ₁p ₆₉₄₅ =p ₆₉₄₅ ⊕i ₁ p ₆₉₉₈ =p ₆₉₉₈ ⊕i ₁p ₇₅₉₆ =p ₇₅₉₆ ⊕i ₁ p ₈₂₈₄ =p ₈₂₈₄ ⊕i ₁p ₈₅₂₀ =p ₈₅₂₀ ⊕i ₁  [Math figure 7]

4) For the 361st information bit i360, the addresses of the parity bitaccumulators are given in the second row of the addresses of paritycheck matrix. In a similar manner the addresses of the parity bitaccumulators for the following 359 information bits is, s=361, 362, . .. , 719 are obtained using the Math figure 6, where x denotes theaddress of the parity bit accumulator corresponding to the informationbit i360, i.e., the entries in the second row of the addresses of paritycheck matrix.

5) In a similar manner, for every group of 360 new information bits, anew row from addresses of parity check matrixes used to find theaddresses of the parity bit accumulators.

After all of the information bits are exhausted, the final parity bitsare obtained as follows:

6) Sequentially perform the following operations starting with i=1p _(i) =p _(i) ⊕p _(i-1) , i=1,2, . . . ,N _(ldpc) −K _(ldpc)−1  [Mathfigure 8]

where final content of pi, i=0, 1, . . . N_(ldpc)−K_(ldpc)−1 is equal tothe parity bit pi.

TABLE 30 Code Rate Qldpc 5/15 120 6/15 108 7/15 96 8/15 84 9/15 7210/15  60 11/15  48 12/15  36 13/15  24

This LDPC encoding procedure for a short FECBLOCK is in accordance witht LDPC encoding procedure for the long FECBLOCK, except replacing thetable 30 with table 31, and replacing the addresses of parity checkmatrix for the long FECBLOCK with the addresses of parity check matrixfor the short FECBLOCK.

TABLE 31 Code Rate Qldpc 5/15 30 6/15 27 7/15 24 8/15 21 9/15 18 10/15 15 11/15  12 12/15  9 13/15  6

FIG. 23 illustrates a bit interleaving according to an embodiment of thepresent invention.

The outputs of the LDPC encoder are bit-interleaved, which consists ofparity interleaving followed by Quasi-Cyclic Block (QCB) interleavingand inner-group interleaving.

shows Quasi-Cyclic Block (QCB) interleaving and (b) shows inner-groupinterleaving.

The FECBLOCK may be parity interleaved. At the output of the parityinterleaving, the LDPC codeword consists of 180 adjacent QC blocks in along FECBLOCK and 45 adjacent QC blocks in a short FECBLOCK. Each QCblock in either a long or short FECBLOCK consists of 360 bits. Theparity interleaved LDPC codeword is interleaved by QCB interleaving. Theunit of QCB interleaving is a QC block. The QC blocks at the output ofparity interleaving are permutated by QCB interleaving as illustrated inFIG. 23, where Ncells=64800/η mod or 16200/η mod according to theFECBLOCK length. The QCB interleaving pattern is unique to eachcombination of modulation type and LDPC code rate.

After QCB interleaving, inner-group interleaving is performed accordingto modulation type and order (η mod) which is defined in the below table32. The number of QC blocks for one inner-group, NQCB_IG, is alsodefined.

TABLE 32 Modulation type ηmod NQCB_IG QAM-16 4 2 NUC-16 4 4 NUQ-64 6 3NUC-64 6 6 NUQ-256 8 4 NUC-256 8 8 NUQ-1024 10 5 NUC-1024 10 10

The inner-group interleaving process is performed with NQCB_IG QC blocksof the QCB interleaving output. Inner-group interleaving has a processof writing and reading the bits of the inner-group using 360 columns andNQCB_IG rows. In the write operation, the bits from the QCB interleavingoutput are written row-wise. The read operation is performed column-wiseto read out m bits from each row, where m is equal to 1 for NUC and 2for NUQ.

FIG. 24 illustrates a cell-word demultiplexing according to anembodiment of the present invention.

shows a cell-word demultiplexing for 8 and 12 bpcu MIMO and (b) shows acell-word demultiplexing for 10 bpcu MIMO.

Each cell word (c0,l, c1,l, . . . , cη mod−1,l) of the bit interleavingoutput is demultiplexed into (d1,0,m, d1,1,m . . . , d1,η mod−1,m) and(d2,0,m, d2,1,m . . . , d2,η mod−1,m) as shown in (a), which describesthe cell-word demultiplexing process for one XFECBLOCK.

For the 10 bpcu MIMO case using different types of NUQ for MIMOencoding, the Bit Interleaver for NUQ-1024 is re-used. Each cell word(c0,l, c1,l, . . . , c9,l) of the Bit Interleaver output isdemultiplexed into (d1,0,m, d1,1,m . . . , d1,3,m) and (d2,0,m, d2,1,m .. . , d2,5,m), as shown in (b).

FIG. 25 illustrates a time interleaving according to an embodiment ofthe present invention.

(a) to (c) show examples of TI mode.

The time interleaver operates at the DP level. The parameters of timeinterleaving (TI) may be set differently for each DP.

The following parameters, which appear in part of the PLS2-STAT data,configure the TI:

DP_TI_TYPE (allowed values: 0 or 1): Represents the TI mode; ‘0’indicates the mode with multiple TI blocks (more than one TI block) perTI group. In this case, one TI group is directly mapped to one frame (nointer-frame interleaving). ‘1’ indicates the mode with only one TI blockper TI group. In this case, the TI block may be spread over more thanone frame (inter-frame interleaving).

DP_TI_LENGTH: If DP_TI_TYPE=‘0’, this parameter is the number of TIblocks NTI per TI group. For DP_TI_TYPE=‘1’, this parameter is thenumber of frames PI spread from one TI group.

DP_NUM_BLOCK_MAX (allowed values: 0 to 1023): Represents the maximumnumber of XFECBLOCKs per TI group.

DP_FRAME_INTERVAL (allowed values: 1, 2, 4, 8): Represents the number ofthe frames IJUMP between two successive frames carrying the same DP of agiven PHY profile.

DP_TI_BYPASS (allowed values: 0 or 1): If time interleaving is not usedfor a DP, this parameter is set to ‘1’. It is set to ‘0’ if timeinterleaving is used.

Additionally, the parameter DP_NUM_BLOCK from the PLS2-DYN data is usedto represent the number of XFECBLOCKs carried by one TI group of the DP.

When time interleaving is not used for a DP, the following TI group,time interleaving operation, and TI mode are not considered. However,the Delay Compensation block for the dynamic configuration informationfrom the scheduler will still be required. In each DP, the XFECBLOCKsreceived from the SSD/MIMO encoding are grouped into TI groups. That is,each TI group is a set of an integer number of XFECBLOCKs and willcontain a dynamically variable number of XFECBLOCKs. The number ofXFECBLOCKs in the TI group of index n is denoted by N×BLOCK_Group (n)and is signaled as DP_NUM_BLOCK in the PLS2-DYN data. Note thatN×BLOCK_Group(n) may vary from the minimum value of 0 to the maximumvalue N×BLOCK_Group_MAX (corresponding to DP_NUM_BLOCK_MAX) of which thelargest value is 1023.

Each TI group is either mapped directly onto one frame or spread over PIframes. Each TI group is also divided into more than one TI blocks(NTI), where each TI block corresponds to one usage of time interleavermemory. The TI blocks within the TI group may contain slightly differentnumbers of XFECBLOCKs. If the TI group is divided into multiple TIblocks, it is directly mapped to only one frame. There are three optionsfor time interleaving (except the extra option of skipping the timeinterleaving) as shown in the below table 33.

TABLE 33 Mode Description Option- Each TI group contains one TI blockand is mapped directly 1 to one frame as shown in (a). This option issignaled in the PLS2-STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH = ‘1’(N_(TI) = 1). Option- Each TI group contains one TI block and is mappedto more 2 than one frame. (b) shows an example, where one TI group ismapped to two frames, i.e., DP_TI_LENGTH = ‘2’ (P_(I) = 2) andDP_FRAME_INTERVAL (I_(JUMP) = 2). This provides greater time diversityfor low data-rate services. This option is signaled in the PLS2-STAT byDP_TI_TYPE = ‘1’. Option- Each TI group is divided into multiple TIblocks and is mapped 3 directly to one frame as shown in (c). Each TIblock may use full TI memory, so as to provide the maximum bit-rate fora DP. This option is signaled in the PLS2-STAT signaling by DP_TI_TYPE =‘0’ and DP_TI_LENGTH = NTI, while P_(I) = 1.

In each DP, the TI memory stores the input XFECBLOCKs (output XFECBLOCKsfrom the SSD/MIMO encoding block). Assume that input XFECBLOCKs aredefined as(d _(n,s,0,0) ,d _(n,s,0,1) , . . . ,d _(n,s,0,N) _(cells) ₋₁ ,d_(n,s,1,0) , . . . ,d _(n,s,0,N) _(cells) ₋₁ , . . . ,d _(n,s,N)_(xBLOCK—TI) _((n,s)-1,0) , . . . ,d _(n,s,N) _(xBLOCK—TI) _((n,s)-1,N)_(cells) ₋₁),where d_(n,s,r,q) is the qth cell of the rth XFECBLOCK in the sth TIblock of the nth TI group and represents the outputs of SSD and MIMOencodings as follows

$d_{n,s,r,q} = \left\{ \begin{matrix}{f_{n,s,r,q},} & {{the}\mspace{14mu}{output}\mspace{14mu}{of}\mspace{14mu}{SSD}\mspace{14mu}\ldots\mspace{14mu}{encoding}} \\{g_{n,s,r,q},} & {{the}\mspace{14mu}{output}\mspace{14mu}{of}\mspace{14mu}{MIMO}\mspace{14mu}{{encoding}.}}\end{matrix} \right.$

In addition, assume that output XFECBLOCKs from the time interleaver5050 are defined as(h _(n,s,0) ,h _(n,s,1) , . . . ,h _(n,s,i) , . . . ,h _(n,s,N)_(xBLOCK—TI) _((n,s)×N) _(cells) ₋₁)

where h_(n,s,i) is the ith output cell (for i=0, . . . , N_(xBLOCK) _(_)_(TI)(n,s)×N_(cells)−1) in the sth TI block of the nth TI group.

Typically, the time interleaver will also act as a buffer for DP dataprior to the process of frame building. This is achieved by means of twomemory banks for each DP. The first TI-block is written to the firstbank. The second TI-block is written to the second bank while the firstbank is being read from and so on.

The TI is a twisted row-column block interleaver. For the sth TI blockof the nth TI group, the number of rows N_(r) of a TI memory is equal tothe number of cells N_(cells), i.e., N_(r)=N_(cells) while the number ofcolumns N_(c) is equal to the number N_(xBLOCK) _(_) _(TI)(n,s)

Hereinafter, the input formatting module/step and output formattingmodule/step in the method of transmitting and receiving a broadcastsignal described above will be described additionally.

As described above with reference to FIG. 1, the input formatting moduleof the broadcast transmitter may demultiplex an input stream to at leastone data pipe (DP) and the input stream may be input as IPstreams/packets, MPEG-2 TS, or a type of generic stream. Also, asillustrated in FIGS. 2 through 4, the input formatting module mayinclude a mode adaptation module and a stream adaptation module. Asillustrated in FIGS. 2 and 3, the mode adaptation module slices inputdata stream and insert the same to a data field of a baseband (BB)frame. Hereinafter, operations of a broadcast signal transmitter and abroadcast signal receiver in a case in which input and output streamsare IP streams will be described. In the present disclosure, thebroadcast signal transmitter may also be referred to as a broadcasttransmitter or a broadcast signal transmission apparatus and thebroadcast signal receiver may also be referred to as a broadcastreceiver or a broadcast signal reception apparatus.

FIG. 26 is a view illustrating a mode adaptation module of a broadcastsignal transmitter according to an embodiment of the present invention.

The mode adaptation module of FIG. 26 is included in the inputformatting module of FIG. 1, and is another embodiment of the modeadaptation module illustrated in FIGS. 2 and 3.

The mode adaptation module of FIG. 26 processes a multi-input stream,and as illustrated in FIGS. 2 and 3 described above, the mode adaptationmodule of FIG. 26 slices an incoming data stream and inserts the same toa data field of a baseband frame. Blocks and modules corresponding tothe blocks and modules described above with reference to FIGS. 2 and 3will be described briefly.

A preprocessing module 26010 may also be referred to as an input streamsplitter module and split an input data stream into multiple services orservice components. An input interface module 26020 may map input datato an internal logical-bit format. An input stream synchronizer module26030 may also be referred to as an ISSY, and provides a means (ISSYinformation) guaranteeing a constant bit rate (CBR) and a constantend-to-end transmission delay. A compensating delay module 26040 candelay the split TS packet stream following the insertion of ISSYinformation to allow a TS packet recombining mechanism without requiringadditional memory in the receiver. A null packet deletion module 26060is used only for the TS input stream case. In FIG. 26, the inputinterface module 26020 and other dotted lined modules 26030, 26040, and26060 may be used when an input stream is a TS stream, and may beomitted or input data may be bypassed when an IP stream/IP packet isprocessed as in the present invention.

As described above, the header compression module 26050 may performpacket header compression to increase transmission efficiency withrespect to an IP input stream. In particular, the header compressionmodule 26050 may use a technique of compressing a plurality of IPheaders, and this will be described in detail hereinafter.

A BB frame header insertion module 26070 may insert a BB frame header toa front end of a BB frame. In FIG. 26, the BB frame header insertionmodule 26070 may also play the role of the BB frame slicer 3060 of FIG.3. However, according to embodiments, the BB frame slicer may beseparately provided, and in this case, the BB frame slicer may allocatedata of IP packets to payload of a BB frame, and the BB frame headerinsertion module 26070 may insert a BB frame header in front of payloadof the BB frame. In the present invention, the BB frame header insertionmodule 26070 may insert information related to IP header compression (IPheader compression information) used in the header compression module26050 into a BB frame header, and the IP header compression informationmay be inserted into an extension field of the BB frame header. Thiswill be described in more detail hereinafter.

The BB frame header may also be referred to as a BB frame header part.The BB frame header or the BB frame header part is a data part in frontof payload in a BB frame. According to embodiments, an essential portionof the BB frame header part may be referred to as a BB frame header, butin this disclosure, the BB frame header may refer to the data part infront of payload of a BB frame. Also, hereinafter, an IP packet may bereferred to as a packet, and an IP packet header may be referred to as apacket header.

FIG. 27 is a view illustrating an output processor module of thebroadcast signal receiver according to an embodiment of the presentinvention.

The output processor module of FIG. 27 may correspond to the outputprocessor module 9030 of the broadcast signal receiver of FIG. 9.

The output processor module may include at least one among a BB frameheader parser module 27010, a null packet insertion module 27020, aheader de-compression module 27030, a di-jitter buffer module 27040, apacket recombining module 27050, and a TS clock regeneration module27060. In particular, the null packet insertion module 27020, thedi-jitter buffer module 27040, and the TS clock regeneration module27060 may be omitted or bypass reception data in case of processing anIP stream/IP packet.

The BB frame header parser module 27010 may parse data of a header partincluded in a BB frame to obtain various types of signaling information.In the present invention, the BB frame header parser module 27010 parsesa BB frame header to obtain IP header compression information includedin an extension field.

The header de-compression module 27030 may de-compress IP headerscompressed in a transmitter. Here, the header de-compression module27030 may decode IP headers through an appropriate method using headercompression information obtained from the BB frame header parser module27010.

The packet recombining module 27050 may combine IP packets to output anIP stream. The IP stream may be recovered in units of service so as tobe output.

FIG. 28 is a view illustrating an IP header compression method accordingto an embodiment of the present invention.

The broadcast transmitter may compress an IP header by using a pluralityof methods. For example, header compression techniques such as a headercompression for broadcasting (HCfB) method, a U-mode method of robustheader compression (ROHC), and the like, may be used. With thesemethods, in case of a stream in which IP fields, excluding a packetlength, are the same, IP packets may be compressed by using a scheme inwhich full IP header information is sent once for the first time andonly changed values are transmitted in the IP header in subsequent IPstreams.

As illustrated in FIG. 28, for IP packets following the IP packet havinga full header, only information different from the full header may betransmitted as a partial header, thereby reducing signaling overhead.

For example, in a case in which an input stream is an IPv4/UDP stream,an IP packet has an IP header of a total of 28 bytes. In case ofcompressing the header by using the HCfB method, a full header may becompressed to 23 bytes and a partial header may be compressed to 5bytes. In a case in which an input stream is an IPv6/UDP stream, an IPpacket has an IP header of a total of 48 bytes. In case of compressingby using the HCfB method, a full header may be compressed to 45 bytesand a partial header may be compressed to 3 bytes.

The compressed headers do not include packet length information, and thepacket length information may be transmitted through an additionalencapsulation header using an encapsulation scheme. In other words, anencapsulation header including header compression (HC) information isadded to each of the compressed IP packets, and the header compressioninformation may include length information of the IP packets.

In another example, an integrated service digitalbroadcasting-terrestrial (ISDB-T) system uses a type length value (TLV)scheme as a compression method, and signals a packet length by using a4-byte TLV header. Also, in this scheme, 4-byte encapsulation headerexists in front of every compressed packet.

In case of an embodiment in which packet length information is signaledthrough a separate additional header, while compressing an IP packetheader, signaling overhead occurs and processing of packets may not beeffective. Thus, the present invention proposes another method inconjunction therewith.

FIG. 29 is a view illustrating an IP header compression method accordingto another embodiment of the present invention.

Referring to FIG. 29, a scheme of using an extension field of a BBframe, rather than the foregoing encapsulation scheme, is proposed as ascheme of transmitting header compression information of an IP packet inan IP direct transmission scheme.

In FIG. 29, the broadcast transmitter may compress IP packets in themanner as that of the method described above with reference to FIG. 28.In this embodiment, however, the broadcast transmitter uses a method ofsignaling IP header compression information by inserting it into aheader of a BB frame, rather than signaling the IP header compressioninformation as a separate additional header through encapsulation.

The IP header compression information signaled in a header of a BB framemay include at least one of a start position of an IP packet, an IPheader compression scheme, or a packet type. A start position of an IPpacket may be signaled in a BB frame or may be signaled as an IP packetlength such that a position can be known by using a length of IPpackets. The IP header compression information may also be referred toas header compression information in this disclosure, and hereinafter,an embodiment of a method of signaling header compression informationwill be described additionally.

FIG. 30 is a view illustrating a method of signaling compressioninformation according to an embodiment of the present invention.

In the embodiment of FIG. 30, a BB frame header may include at least oneof a STUFFI field, a SYNCD field, an EXTI field, an RFU field, or anExtension field. However, according to embodiments, the configuration ofthe BB frame header and order of the fields may be altered.

The STUFFI field describes whether the stuffing field is or is notwithin the BBF. If STUFFI=‘0’, the BBF does not include the stuffingfield and the in-band signaling field. Otherwise, the BBF has thestuffing field or the in-band signaling field.

The SYNCD field describes the distance in bytes from the beginning ofthe data field to the beginning of the first transmitted UP that startsin the data field. SYNCD=0_D means that the first UP is aligned to thebeginning of the data field. SYNCD=8191_D means that no UPs starts inthe data field.

The RFU (1-bits) field is reserved for future use. In this embodiment,2-bit RFU field is changed to 1-bit RFU field and 1 bit is allocated toan EXTI field.

The EXTI field indicates whether an extension field exists.

In a case in which an extension field is used to signal IP headercompression information as described above, the extension field may beconfigured as shown in Table 34 of FIG. 30. Table 34 shows an embodimentof syntax of an extension field/table for transmitting IP headercompression information, and a specific syntax and the number ofallocated bits are not limited thereto.

Descriptions of the fields included in Table 34 are as follows.

extension_type field is a field distinguishing the purpose of anextension field and may be set to a type regarding header compression.

header_compression_mode indicates an IP header compressions scheme inuse. For example, it may indicate the foregoing HCfB scheme, the U-modescheme of RoHC, and the like.

num_ip_packet may indicate the number (N) of IP packet headers includedin a corresponding BB frame. This field has N number of packet_typefields and packet_start_position fields.

packet_type indicates a type of a compressed IP packet and may beconfigured as illustrated in Table 35.

Thereafter, in order to align a final field length by byte, a reserved(0 to 7 bits) may be included.

Finally, a CRC may be inserted to perform an error check function of theextension field.

Table 35 describes a packet_type field.

A field value 000 indicates that a header of a compressed packet is afull IP header. Namely, the field value 000 is used when a compressed IPpacket/header is a newly defined full IP header without having a commoncompression ID (CID) such as a partial packet which is previouslytransmitted. Such a header may be referred to as a new full IP header.

A field value 001 indicates that a compressed packet header is a full IPheader. Namely, the field value 001 is used when a compressed IPpacket/header has the same CID as that of a previously transmittedpartial packet. Such a header may be referred to as a continuous full IPheader.

A field value 010 is used when a header of a compressed packet is apartial IP header.

A field value 111 is used to transmit information assisting IP headercompression.

Other remaining fields may be used as reserved fields that may be addedlater.

The packet_type field will be described in addition, and a full IPheader may be transmitted a plurality of times in order to decodepartial headers of a plurality of subsequent IP packets. For example,full IP headers may be transmitted at predetermined intervals to ensureefficiency of decoding, as well as for a case in which contents of an IPheader is changed. The full IP headers which are not changed in contentsand repeatedly transmitted may be identified by the field value 001. Ina case in which the packet_type field value is 000, an IP full header asa new one may be used to recover information of subsequent partialheaders, and in a case in which the field value is 001, the IP fullheader, as a repeated one, may be used to recover information ofsubsequent partial headers and preceding partial headers.

FIG. 31 is a view illustrating a method for signaling header compressioninformation according to another embodiment of the present invention.

Also, in an embodiment of the present invention, a BB frame header mayinclude a STUFFI field, a SYNCD field, an EXTI field, an RFU field, andan Extension field. However, according to embodiments, the configurationof the BB frame header and order of fields may be altered. The BB frameheader structure described above with reference to FIG. 30 anddescriptions thereof will be omitted.

When an extension field is used to signal IP header compressioninformation as described above, the extension field may be configured asshown in Table 36 of FIG. 31. Table 36 shows an embodiment of a syntaxof an extension field/table for transmitting IP header compressioninformation, and a specific syntax and the number of allocated bits arenot limited thereto. Table 36 shows a light version for reducingoverhead, compared with Table 34.

Descriptions of the fields included in Table 36 are as follows.

packet_type (3 bits) field is a type of a compressed IP packet and maybe configured like Table 35 of FIG. 30.

end_flag (1 bit) field is a field indicating whether a header is a finalpacket header in a BBA frame, by which a while loop may be terminated.If a field (ith field) is a final field, end_flag is set to 1 to have aCRC field. If there is a (i+1)th field exists subsequently, the end_flagis set to 0 to have (i+1)th packet_type, end_flag, andpacket_start_position field again.

packet_start_position field (13 bits) indicates a position in which anew packet starts, and may be signaled as an absolute position in a BBframe.

A unit is a byte unit, and 13 bits are allocated by a maximum of 8Kbytes.

Thereafter, in order to align a final field length by byte, a reservedfield (0 to 7 bits) is included.

Finally, a CRC is inserted to perform an error check function of theextension field.

In FIGS. 30 and 31, the method in which a position of a packet issignaled as a start point has been described. Hereinafter, a method inwhich a position of a packet is signaled by using a packet length willbe described with reference to FIGS. 32 and 33

FIG. 32 is a view illustrating a method of signaling header compressioninformation according to another embodiment of the present invention.

Also, in this embodiment, a BB frame header may include a STUFFI field,a SYNCD field, an EXTI field, an RFU field, and an Extension field.However, according to embodiments, the configuration of the BB frameheader and order of fields may be altered. The BB frame header structuredescribed above with reference to FIG. 30 and descriptions thereof willbe omitted.

When an extension field is used to signal IP header compressioninformation as described above, the extension field may be configured asshown in Table 37 of FIG. 32. Table 37 shows an embodiment of a syntaxof an extension field/table for transmitting IP header compressioninformation, and a specific syntax and the number of allocated bits arenot limited thereto.

Descriptions of the fields included in Table 37 are as follows.

packet_type (2 bits) field is a type of a compressed IP packet and maybe configured like Table 35 of FIG. 30.

end_flag (1 bit) field is a field indicating whether a header is a finalpacket header in a BBA frame, by which a while loop may be terminated.If a field (ith field) is a final field, end_flag is set to 1 to have aCRC field. If there is a (i+1)th field exists subsequently, the end_flagis set to 0 to have (i+1)th packet_type, end_flag, and packet_lengthfield again.

mtu_mode and packet_length are used to effectively express acorresponding packet length and implemented by using a variable mappingrule. mtu is a maximum transmission unit.

mtu_mode (1˜4 bits) field serves to indicate a maximum value of a packetlength, and accordingly, the number of allocated bits of a packet lengthis varied.

packet_length (11˜16 bits) field indicates length information of acorresponding packet, and the number of allocated bits is variedaccording to mtu_mode.

Thereafter, in order to align a final field length by byte, a reservedfield (0 to 7 bits) is included.

Finally, a CRC is inserted to perform an error check function of theextension field.

The packet_type table of Table 35 is as described above with referenceto FIG. 30. Also, the foregoing table, an embodiment according to theTLV scheme, may be altered according to header compression schemes

FIG. 33 is a view illustrating an embodiment regarding a scheme ofexpressing a packet length.

As described above with reference to FIG. 32, in order to express apacket length by a minimum of bits, a mtu_mode field and a packet_lengthfield having a variable field length may be used. In other words, inorder to enhance transmission efficiency, a packet length is dividedinto certain sections and signaling is performed according to asubtable.

Table 38 of FIG. 33 is a table illustrating field vales of the mtu_modefield according to lengths of an IP packet and packet_length field sizecorresponding thereto.

In a case in which a packet size is 4095 or smaller, the mtu_mode fieldis set to 0 as 1 bit, and thereafter, a packet size is indicated byusing 12 bits in the packet_length field. In this case, the entirefields a total of 16 bits by adding the packet_type (2 bits) and anend_flag (1 bit).

In a case in which the packet size ranges from 4096 to 8191, themtu_mode field is set to 10 as 2 bits, and thereafter, a packet size isindicated by using 13 bits in the packet_length field. In this case, theentire fields a total of 18 bits by adding the packet_type (2 bits) andthe end_flag (1 bit).

In a case in which the packet size ranges from 8192 to 16383, themtu_mode field is set to 110 as 3 bits, and thereafter, a packet size isindicated by using 14 bits in the packet_length field. In this case, theentire fields a total of 20 bits by adding the packet_type (2 bits) andthe end_flag (1 bit).

In a case in which the packet size ranges from 16384 to 32767, themtu_mode field is set to 1110 as 4 bits, and thereafter, a packet sizeis indicated by using 15 bits in the packet_length field. In this case,the entire fields a total of 22 bits by adding the packet_type (2 bits)and the end_flag (1 bit).

In a case in which the packet size ranges from 32768 to 65535, themtu_mode field is set to 11110 as 5 bits, and thereafter, a packet sizeis indicated by using 16 bits in the packet_length field. In this case,the entire fields have a total of 24 bits by adding the packet_type (2bits) and the end_flag (1 bit).

In the case of using such a packet size representation scheme, anoperation may be performed by the minimum packet capacity. However, inthe encapsulation scheme described above, since the packet length isexpressed by byte, and thus, 16 bits may be expressed as 2 bytes, but incase of 18 bits, 3 bytes are required to express it, generating (bytealignment) overhead.

In contrast, in the embodiment of FIGS. 32 and 33, since they arecontinuously configured in the BB frame header, fields not formed bybyte may be added and byte alignment may be finally performed only once,thus reducing overhead. In other words, in the present invention, wheninformation is allocated to the BB frame header, the information isallocated by bit unit, and fields not formed by byte, among theallocated information, are added to finally configure information bybyte unit.

For example, three packets having a length of 2000 bytes are configuredas in Case 1 of FIG. 33, three packets are configured by 2-byte fieldsthrough the proposed method, and in this case, a total of 6 bytes arerequired to describe the packet length.

In contrast, in the encapsulation scheme described above, for example,in case of the TLV scheme, three encapsulation headers of 4 bytes perpacket are required, requiring a total of 12 bytes. In the case of GSE,6 bytes are finally required.

In a case in which three packets having lengths of 4100, 2200, and 4200are included, the packets may be expressed as 2.25, 2, and 2.25 bytes,respectively, in the proposed method, and in order to align the packetsby 8 bits, 4-bit reserved is used, and thus, 7 bytes are finallyrequired. In other words, since the packet lengths are expressed by 18bits, 16 bits, and 18 bits in bit unit, respectively, and 4 bits areadded, totaling 56 bits, and thus, when the bits are aligned as byte, 7bytes are obtained.

Meanwhile, in case of GSE, 26 bytes are required, and in case of TLV, 12bytes are required.

In addition, among the fields collected in the BB frame header, an errorcheck may be performed by using a CRC field.

In case of compressing a header of an IP packet, the encapsulationscheme of adding header compression information to each IP packetdescribed above with reference to FIG. 288 or the scheme of includingheader compression information in a BB frame header described above withreference to FIGS. 29 through 33 may be used. Hereinafter, thedifference between the encapsulation scheme and the scheme proposed bythe present invention will be described in detail.

FIG. 34 illustrates a configuration of a BB frame according to IP headercompression methods according to an embodiment of the present invention.

As described above, a) in the encapsulation method, IP headercompression information including packet length information is added asan encapsulation header to each IP packet, and b) in the proposedmethod, IP header compression information is added as a table/field to aBB frame header.

In the encapsulation method, the encapsulation header is added to everyIP packet, indicating length information of compressed IP packets. Thelength of the compressed IP packet may be expressed by a maximum of 16bits, and in the TLV scheme, 4 bytes are fixedly used. In the case ofGSE, a short IP packet has low overhead as 2 bytes, but as the IP packetlength increases, a header may increase up to 59 bytes. Also, theencapsulation header should be operated by byte, and thus, it isdifficult to optimize transmission efficiency.

In contrast, however, in the proposed method, since a start point ofeach packet is pointed in a BB frame header, instead of transmitting apacket length, only a maximum of 13 bits to a minimum of 10 bits may beused according to code rates and LDPC sizes. Also, in case oftransmitting a packet length, required information may be signaled by asignificantly smaller amount of data by using the mtu_mode field andTable 38. In addition, since every information is defined in the BBframe header, alignment by byte may be performed once in the frameheader unit, rather than by packet, minimizing overhead and facilitatingfunction extension later.

FIG. 35 illustrates a method of configuring a BB frame according to IPheader compression methods and an error checking method according to anembodiment of the present invention.

As illustrated in FIG. 35, a) in the case of the encapsulation method,if there is an error in a BB frame, it is not possible to check alocation of an IP packet and it is difficult to check whether every IPpacket has an error.

In contrast, b) in the proposed method, since header compressioninformation including IP packet length information is transmitted in aheader of a BB frame by applying a CRC technique, error detectioncapability is provided. Thus, as illustrated in FIG. 35, even though aBB frame has an error, if there is no error in header compressioninformation, a receiver can accurately know positions of IP packets. Thereceiver may use each IP packet by decoding header information andchecking an error by using internal check sum information.

In the case of the encapsulation method, even though only one ofposition information has an error as illustrated in FIG. 35, positionsof all the subsequent packets may become uncertain due to a relativelength of packets. However, in the case of the proposed method, absolutepositions of IP packets in a BB frame are signaled in the BB frameheader, even though one position information has an error, there is noproblem in recognizing positions of other IP packets, excluding thecorresponding IP packet, and obtaining IP header information.

FIG. 36 illustrates a configuration of a BB frame according to IP headercompression methods and a packet access method according to anembodiment of the present invention.

As illustrated in FIG. 36, a) in the case of the encapsulation method, areceiver i) parses received BB frame header information, ii) parses anencapsulation header at a first IP packet position to obtain packetlength information, and iii) subsequently parses an encapsulation headerof a next IP packet position. The receiver repeats this process tosearch for a full IP header, and when a full IP header is searched, thereceiver may decode (or de-compress) a subsequent IP packet header byusing the full IP header.

In contrast, in the case of the proposed method, the receiver i) mayparse received BB frame header information to obtain positioninformation of a full IP header, and ii) decode (de-compress) an IPheader at a corresponding position. Thus, the rate of decompressing theIP packet header and the rate of decoding the IP packet can besignificantly shortened.

In addition to the shortened decoding rate, a) in the case of theencapsulation method, it may happen that an encapsulation header of anIP packet included in a frame is not parsed. For example, an error mayoccur sporadically, and here, if an error occurs in an encapsulationheader position, the receiver may not be able to parse an IP packet eventhough the corresponding IP packet does not have an error. Thus, b) theproposed method can obtain the full IP header more safely and stably.

FIG. 37 illustrates a BB frame configuration and packet access methodaccording to an embodiment of the present invention.

According to the proposed method, the receiver may obtain typeinformation and position information of an IP packet header by parsing aBB frame header. In particular, when a full IP header is set to continueas described above, it means that a CID value of a preceding partial IPheader and a CID value of a subsequent full IP header are identical.Namely, when the full IP header set to continue is obtained, thepreceding partial IP headers having the same CID may be decoded by usingthe obtained full IP header, without having to search for the precedingfull IP header, allowing for faster packet accessing.

FIG. 38 is a view illustrating a method for transmitting a broadcastsignal according to an embodiment of the present invention.

Regarding a broadcast transmitter and an operation thereof, as describedabove, a broadcast signal transmitter may demultiplex an input streaminto at least one data pipe (DP) by using an input formatting module(S38010). The broadcast transmitter may perform error correctionprocessing on data included in at least one DP by using a BICM module(S38020). The broadcast signal transmitter may map the data of the DP toa symbol of a signal frame to generate a signal frame including the dataof the DP, by using a frame building module (S38030). The broadcastsignal transmitter may insert a preamble into a transmission signal andperform OFDM modulation thereon by using an OFDM generation module(S38040).

The broadcast transmitter may perform additional processing on an IPframe by using the input formatting module. Namely, the broadcasttransmitter may compress IP packets included in an IP stream by using aheader compression module, allocate the IP packets to a BB frame byusing a BB frame slicer module, and insert a BB frame header includingIP header compression information into the BB frame by using a BB frameheader insertion module.

As described above with reference to FIGS. 28 through 33, the broadcasttransmitter may compress headers of IP packets included in an IP stream,and insert related IP header compression information into a BB frameheader. The IP header compression information may include IP packetposition information, IP packet type information, and the like, and maybe included in the BB frame header. The IP packet position informationmay be signaled as start position information of IP packets within asignal frame as illustrated in FIGS. 30 and 31, or may be signaled asposition information of the IP packets as illustrated in FIGS. 32 and33. The IP header compression information includes various types ofinformation as illustrated in the Tables described above with referenceto FIGS. 28 through 33, and may be included in various formats in the BBframe header. The IP header compression information may be included inan extension field of the BB frame header part, but the position of theinformation may not be limited thereto.

FIG. 39 is a view illustrating a method for receiving a broadcast signalaccording to an embodiment of the present invention.

Regarding a broadcast receiver and an operation thereof, as describedabove, a broadcast signal receiver may perform signal detection and OFDMdemodulation on a reception broadcast signal by using asynchronization/demodulation module (S39010). The broadcast receiver mayextract service data by parsing a signal frame of the receptionbroadcast signal by using a frame parsing module (S39020). The broadcastreceiver may convert service data extracted from the reception broadcastsignal into a bit domain and perform deinterleaving thereon by using ademapping and decoding module (S39030). The broadcast receiver mayoutput service data processed by using an output processing module, as adata stream (S39040).

The broadcast receiver may perform additional processing on an IP streamby using the output processing module. Namely, the broadcast receivermay obtain IP header compression information by parsing a BB frameheader of the reception broadcast signal by using a BB frame headerparser module. The broadest receiver may de-compress headers of IPpackets included in a BB frame by using the IP header compressioninformation through a header de-compression module. The broadcastreceiver may combine IP packets by using a packet recombining module tooutput an IP stream.

As described above with reference to FIGS. 28 through 33, headers of theIP packets included in the IP stream are compressed, and the related IPheader compression information may be included in the BB frame header.The IP header compression information may include IP packet positioninformation, IP packet type information, and the like. The IP packetposition information may be signaled as start position information of IPpackets within a signal frame as illustrated in FIGS. 30 and 31, or maybe signaled as position information of the IP packets as illustrated inFIGS. 32 and 33. The IP header compression information includes varioustypes of information as illustrated in the Tables described above withreference to FIGS. 28 through 33, and may be included in various formatsin the BB frame header. The IP header compression information may beincluded in an extension field of the BB frame header part, but theposition of the information may not be limited thereto.

In the specification, methods and apparatuses for receiving andtransmitting a broadcast signal are used.

It will be appreciated by those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both of the apparatus and method inventions may becomplementarily applicable to each other.

What is claimed is:
 1. An apparatus for transmitting a broadcast signal,the apparatus comprising: an input formatter module configured tode-multiplex an input stream into at least one data pipe (DP); a BitInterleaved Coding and Modulation (BICM) module configured to performerror correction on data of the at least one DP; a frame building moduleconfigured to generate a signal frame including the data of the at leastone DP; and an Orthogonal Frequency Division Multiplexing (OFDM))generation module configured to generate a transmission signal byinserting a preamble into the signal frame and performing OFDMmodulation, wherein the input formatter module comprises: a headercompression module configured to compress Internet Protocol (IP) headersof IP packets included in an IP stream into a full header or a partialheader when the input stream is the IP stream; a baseband (BB) frameslicer module configured to allocate data of the IP packets to a BBframe; and a BB frame header insertion module configured to insert a BBframe header into the BB frame, the BB frame header including IP headercompression information, wherein the IP header compression informationincludes IP packet type information and IP packet position informationfor the IP packets, wherein the IP packet position information indicatesa position of each of the IP packets within the BB frame and the IPpacket type information indicates whether each of the IP packetsincludes the full header or the partial header.
 2. The apparatus ofclaim 1, wherein the IP packet position information is inserted insteadof length information in each of the IP headers.
 3. The apparatus ofclaim 1, wherein the IP packet position information is start positioninformation of the IP packets within the signal frame or lengthinformation of the IP packets within the signal frame.
 4. The apparatusof claim 1, wherein the IP header compression information is included inan extension field of the BB frame header.
 5. A method for transmittinga broadcast signal, the method comprising: an input formatting operationof de-multiplexing an input stream into at least one data pipe (DP);BICM processing operation of performing error correction on data of theat least one DF; a frame building operation of generating a signal frameincluding the data of the at least one DP; and an OFDM generatingoperation of generating a transmission signal by inserting a preambleinto the signal frame and performing Orthogonal Frequency DivisionMultiplexing (OFDM) modulation, wherein the input formatting operationof de-multiplexing comprises: compressing Internet Protocol (IP) headersof IP packets included in an IP stream into a full header or a partialheader when the input stream is the IP stream; allocating data of the IPpackets to a baseband (BB) frame; and inserting a BB frame headerincluding IP header compression information into the BB frame, whereinthe IP header compression information includes IP packet typeinformation and IP packet position information for the IP packets,wherein the IP packet position information indicates a position of eachof the IP packets within the BB frame and the IP packet type informationindicates whether each of the IP packets includes the full header or thepartial header.
 6. The method of claim 5, wherein the IP packet positioninformation is inserted instead of length information in each of the IPheaders.
 7. The method of claim 5, wherein the IP packet positioninformation is start position information of the IP packets within thesignal frame or length information of the IP packets within the signalframe.
 8. The method of claim 5, wherein the IP header compressioninformation is included in an extension field of the BB frame header. 9.An apparatus for receiving a broadcast signal, the apparatus comprising:a synchronization/demodulation module configured to perform signaldetection and Orthogonal Frequency Division Multiplexing (OFDM)demodulation on a received broadcast signal; a frame parsing moduleconfigured to parse a signal frame of the broadcast signal to extractservice data; a demapping/decoding module configured to convert an inputsignal into a bit domain and perform deinterleaving on the bit domain;and an output processing module configured to receive the service dataand output a data stream, wherein the output processing modulecomprises: a baseband (BB) frame header parser module configured toparse a BB frame header to obtain Internet Protocol (IP) headercompression information; a header de-compression module configured tode-compress headers of IP packets included in a BB frame by using the IPheader compression information; and a packet recombining moduleconfigured to combine the IP packets to output an IP stream, wherein theIP header compression information includes IP packet type informationand IP packet position information for the IP packets, wherein the IPpacket position information indicates a position of each of the IPpackets within the BB frame and the IP packet type information indicateswhether each of the IP packets includes a full header or a partialheader.
 10. The apparatus of claim 9, wherein the IP packet positioninformation is start position information of the IP packets within thesignal frame or length information of the IP packets within the signalframe.
 11. The apparatus of claim 9, wherein the IP header compressioninformation is included in an extension field of the BB frame header.12. A method for receiving a broadcast signal, the method comprising: asynchronization/demodulation operation of-performing signal detectionand Orthogonal Frequency Division Multiplexing (OFDM) demodulation on areception broadcast signal; a frame parsing operation of parsing asignal frame of the reception broadcast signal to extract service data;a demapoping/decoding operation converting an input signal into a bitdomain and performing deinterleaving on the bit domain; and an outputprocessing operating of receiving the service data and outputting a datastream, wherein the output processing operation of receiving the servicedata and outputting the data stream comprises: a baseband (BB) frameheader parsing operation of parsing a BB frame header to obtain IPheader compression information; a header de compression operation ofde-compressing headers of IP packets included in a BB frame by using theIP header compression information; and a packet recombining operation ofcombining the IP packets to output an IP stream, wherein the IP headercompression information includes IP packet type information and IPpacket position information for the IP packets, wherein the IP packetposition information indicates a position of each of the IP packetswithin the BB frame and the IP packet type information indicates whethereach of the IP packets includes a full header or a partial header. 13.The method of claim 12, wherein the IP packet position information isstart position information of the IP packets within the signal frame orlength information of the IP packets within the signal frame.
 14. Themethod of claim 12, wherein the IP header compression information isincluded in an extension field of the BB frame header.